This release is a pre-release and may not be stable for production use.
rtest
A Python test runner built with Rust, featuring high-performance test collection and parallel test execution.
⚠️ Development Status: This project is in early development (v0.0.x). Expect bugs, breaking changes, and evolving features as we work toward stability.
Performance
rtest discovers tests through static AST analysis without importing test modules. CI measures collection on fixed
Click, Flask, and Pydantic source revisions using a release build, 3 warmups, and 20 measured runs.
The benchmark job publishes timings, collected test IDs, and raw Hyperfine reports. See the benchmark guide to reproduce a run.
Static discovery and pytest's import-based collection perform different work and can discover different tests. The benchmark reports collection time only; it does not claim equivalent test coverage, execution speedups, or performance regressions across different CI machines.
Quick Start
Installation
pip install rtest
Requires Python 3.10+
Building from source requires Rust 1.97+ and the initialized Ruff submodule (git submodule update --init).
Basic Usage
# Collect tests (fast AST-based collection)
rtest --collect-only
# Run tests with native runner
rtest --runner native
# Run tests in parallel (4 workers)
rtest --runner native -n 4
Native Runner
The native runner (--runner native) executes tests using rtest's own decorators:
import rtest
@rtest.mark.cases("value", [1, 2, 3])
def test_example(value):
assert value > 0
@rtest.mark.skip(reason="Not implemented yet")
def test_skipped():
pass
The native runner respects python_files, python_classes, and python_functions patterns from your
pyproject.toml under [tool.pytest.ini_options].
For compatibility, @pytest.mark.parametrize and @pytest.mark.skip decorators are also supported.
Roadmap
- Fixtures -
@rtest.fixturewith function/class/module scopes and dependency resolution - conftest.py support - Fixture discovery across directory hierarchy
- Distribution modes - Group tests by module/class, optimized scheduling algorithms
- Built-in assertions -
rtest.raises()and other assertion helpers - Additional markers -
@rtest.mark.xfail,@rtest.mark.skipif - Test selection -
-kexpression filtering,--last-failed,--failed-first - Better error formatting - Rich diffs, colorized output, traceback filtering
- Async test support - Native
async def test_*()handling - Watch mode - Re-run tests automatically on file changes
Known Limitations
Parametrized Test Discovery
rtest supports limited static expansion of parametrized tests, including simple uses of:
- Literal values: numbers, strings, booleans, None, lists/tuples of literals
- Module-level constants:
DATA = [1, 2, 3]then@cases("x", DATA) - Class constants:
Config.MAX_SIZE - Enum members:
Color.RED - Nested class constants:
Outer.Inner.VALUE
from enum import Enum
import rtest
class Color(Enum):
RED = 1
GREEN = 2
DATA = [1, 2, 3]
@rtest.mark.cases("value", DATA) # Resolves to [1, 2, 3]
def test_module_constant(value):
assert value > 0
@rtest.mark.cases("color", [Color.RED, Color.GREEN]) # Resolves enum members
def test_enum_values(color):
assert color.value in [1, 2]
When static expansion fails, rtest emits a warning and falls back to the base test name:
@pytest.mark.parametrize("value", get_data()) # Function call
def test_dynamic(value):
assert value > 0
@pytest.mark.parametrize("value", [x for x in range(3)]) # Comprehension
def test_comprehension(value):
assert value > 0
warning: Cannot statically expand test cases for 'test.py::test_dynamic': argvalues contains function call 'get_data'
warning: Cannot statically expand test cases for 'test.py::test_comprehension': argvalues contains a comprehension
In these cases, test execution is still functionally equivalent - pytest automatically runs all parametrized variants when given the base function name.
Project-specific parametrize decorators
Projects that wrap pytest.mark.parametrize in their own decorator can describe the wrapper in pyproject.toml so
rtest expands it statically:
[[tool.rtest.parametrize-wrappers]]
decorator = "myproject.testing.parametrize" # fully qualified decorator name
argname = "p" # the single argname the wrapper passes to pytest
record = "myproject.testing.Params" # optional: row type accepted in place of tuples
id-field = "id" # optional: field whose value becomes the test ID
The wrapper is called as @parametrize(argnames, argvalues, ids=None) and passes every case to the test as one
argname argument: argvalues that are already record calls are used as-is, and other rows are zipped with
argnames. IDs come from a static ids= list, then from id-field when the argnames include it, and otherwise
default to {argname}{index}. Anything that cannot be resolved statically falls back to pytest, as above.
Literal-values helpers
Functions that return the values of a Literal type, like typing.get_args, can be listed by qualified name.
Calls with one argument then expand from the type, with unions (A | B or Union[A, B]) flattened left to right:
[tool.rtest]
literal-values-functions = ["myproject.literals.LiteralTools.values"]
Both LiteralTools.values(Color) and LiteralTools[Color].values(Color) resolve. Each Literal keeps its own
de-duplication and union members that are equal as types are dropped, matching typing.get_args; a union member
that is not a Literal of strings falls back to pytest.
Pass-through helpers
Functions that validate their first argument and return it unchanged can be listed by qualified name, so a call resolves to that argument:
[tool.rtest]
passthrough-functions = ["myproject.validation.check_values", "graphql_lib.gql"]
Functions, comprehensions and types
- A function or
@staticmethod/@classmethodwithout parameters whose body is a singlereturn(after an optional docstring) resolves to the returned expression, evaluated in its defining module. - Comprehensions,
set/frozensetliterals and calls,sorted(...),enumerate(...),zip(...)and{**a, ...}evaluate over static values. A set must be sorted before it is used as argvalues, since its iteration order is only known at runtime. - Classes reached through a module (
import pkg.mod,import pkg.mod as m,from pkg import mod) ID by__name__, as do subscripted types:list[int]islist,Optional[int]isOptional, aLiteral[...]isLiteral, and a union of distinct members isUnion(Python drops duplicate members first, soUnion[int, int]isint).int | Nonehas no__name__and is IDed positionally. float("nan")and other plain numeric strings,http.HTTPStatusmembers andpytest.ExitCodemembers (bothIntEnums, IDed by their integer value) resolve to their values.
Records and IDs
Instances of plain record classes are counted statically and IDed positionally, and their attributes can feed IDs
(ids=lambda case: case.name or ids=[case.name for case in CASES]). A record class is a @dataclass without
__init__ or __post_init__ whose only base is another such dataclass (Generic[T] aside), a NamedTuple,
or a class whose __init__ only assigns parameters to
self attributes. Names reached through from module import * follow a static __all__ (or the module's public
names when it has none), and nested classes resolve members through dotted bases such as
class Status(Enums.Status): pass.
Path Separator Handling
rtest uses platform-specific path separators in test nodeids, while pytest normalizes all paths to use forward
slashes (/) regardless of platform. For example:
On Windows:
- pytest shows:
tests/unit/test_example.py::test_function - rtest shows:
tests\unit\test_example.py::test_function
On Unix/macOS:
- Both show:
tests/unit/test_example.py::test_function
This difference is intentional as rtest preserves the native path format of the operating system.
Native Runner Scope
The native runner (--runner native) does not currently support pytest fixtures or conftest.py discovery. Projects
that rely on fixtures should use --runner pytest instead. Fixture support is tracked in
#105.
pytest-xdist Serialization with Decimal Objects
When using --runner pytest -n N (parallel pytest execution), projects that use Decimal objects in parametrized test
data may fail with a serialization error:
execnet.gateway_base.DumpError: can't serialize <class 'decimal.Decimal'>
This is a limitation of pytest-xdist's inter-process communication, which cannot serialize certain Python types. Tests
pass when run without parallelization (--runner pytest without -n). See
#116 for details.
Collection Failures on Complex Codebases
Some projects with complex runtime behavior (e.g., extensive use of plugins, dynamic imports, or metaclass-heavy
patterns) may fail during rtest collection despite working correctly with pytest. For example, the
pydantic repository encounters errors when collected by rtest. See
#55 for details.
Contributing
We welcome contributions! See Contributing Guide.
License
MIT - see LICENSE file for details.
Acknowledgments
This project takes inspiration from Astral and leverages crates from [ruff].
1 maintainer
Metadata
1 maintainer
Release files for rtest-forked-constants 0.0.48rc10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rtest_forked_constants-0.0.48rc10.tar.gz | 1.3 MB | With provenance | Details for rtest_forked_constants-0.0.48rc10.tar.gz |
Built distributions (wheels)
Total release size: 60.9 MB
Release files / rtest_forked_constants-0.0.48rc10.tar.gz
| Download URL | rtest_forked_constants-0.0.48rc10.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
794df4c7977936ac7e7ed11bab2ba1533855b78a635a9e5edc7ac4646390797a
|
|
BLAKE2b-256 checksum How to use checksums |
ae9f193538943aad9f6b6f82e56f14b2d309049e3bde41923b204ad1beacec94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-pp311-pypy311_pp73-manylinux_2_34_aarch64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-pp311-pypy311_pp73-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Linux glibc 2.34+ ARM64 PyPy 3.11 PyPy 3.11 7.3 |
|
SHA-256 checksum How to use checksums |
0bdd36beb6779495dcf33172a84d39e409024f00d29d372a24dc86977431f302
|
|
BLAKE2b-256 checksum How to use checksums |
1ca27e806f3d0f333b143a785e881ed8d39cd623207aa5adf9fded060ec4fe59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-pp311-pypy311_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-pp311-pypy311_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | Linux glibc 2.17+ x86-64 PyPy 3.11 PyPy 3.11 7.3 |
|
SHA-256 checksum How to use checksums |
5e59b3f20de02f10e698ea711b5eb93137ffa85bc7f1d1ea0b14c479cb2709dd
|
|
BLAKE2b-256 checksum How to use checksums |
d8d2a89912a64169336595d133ef8ce00b4ae61d6b524f45a189dbd2094e7b54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp315-cp315t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp315-cp315t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
c76005b70834c0d46779d50a01ef14f8d1a7c5cf45940cd58dd8c7dedffc1031
|
|
BLAKE2b-256 checksum How to use checksums |
41850f2ee76018eee0aede6fe7d54b7c8bc48360564e95f698db8f4b42ad1d20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp315-cp315-win_amd64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp315-cp315-win_amd64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.15 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
4f9b56b75b4c50382d97447febbca5850f6853e0200b4a27bba5e9ae1e93e590
|
|
BLAKE2b-256 checksum How to use checksums |
71363510e03d3c24dc43557677995ef3e5e8aaac88beec9b75726c1c4f83ad5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp315-cp315-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp315-cp315-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.15 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
affeb98160ca57f8eb8dd6a59e684ae3da073e0e0c8a739146392f58fbca8540
|
|
BLAKE2b-256 checksum How to use checksums |
73ac57d6742a3cda1622f62dba640e9e60f6a8884673d43dfa89086f23858cd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp315-cp315-macosx_10_12_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp315-cp315-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.15 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
b25365da71dad856372d6f3a11f3e0afa6fa8929ced348a1180badf61b6d6540
|
|
BLAKE2b-256 checksum How to use checksums |
724af7ce1cb8970a9bded9de8bed8f61ba102b4acce4e247c5887bc2fe1f34b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp314-cp314t-manylinux_2_34_aarch64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp314-cp314t-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
74d5f14111973a4f1e2451edc40f216c45d4f6d9dd23197f47ae42b2e733b252
|
|
BLAKE2b-256 checksum How to use checksums |
2d4724ad92c4e383680bc14a7916d22532d50d508291605ffe5ee042e40c5d1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
4f6f7e8bfe23da1dd3def14d515270407dd7ff0983932058d0bf9d42b29e8a70
|
|
BLAKE2b-256 checksum How to use checksums |
6ef4edede5db237b688a023512c4e606141ae3a35e289e9002274ec7754609b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp314-cp314-win_amd64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8544a2bc0b630df24a10d2e701c5b8bfbed1761450d56568d1622e1db67e0f34
|
|
BLAKE2b-256 checksum How to use checksums |
bc8730b6dedbb1b6801a07a22c43d4a48cdac5156259efe4190831970f7eb350
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp314-cp314-manylinux_2_34_aarch64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp314-cp314-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.14 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
898f3118f67134900c85833852799ea873c3fdffe5147e1ce30b5b6d8e88111f
|
|
BLAKE2b-256 checksum How to use checksums |
6bd9d99b686bc3af938a3f9de2014764d894a3eeb9f380fe21dca227e5186fca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
a730fc663143deeaf6a4dbbe467daf3f7378fa08f5757ef443ec5d3f0293d5ca
|
|
BLAKE2b-256 checksum How to use checksums |
b887d0cd8e37fb42ab075cf2de7b9dc39731b2f5f1f38cb01b0f1da02553946c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
e98b78b398109c732df066224254bb509f523a7c4c21e4db60bc5e3b60f18a76
|
|
BLAKE2b-256 checksum How to use checksums |
7e0e823e68526fe25c698bf28c847b7f608ba8e17753d491791c8e6688069c9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp314-cp314-macosx_10_12_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp314-cp314-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.14 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
c74fd76304da4e3924e708427e9c4cd07ce9ba943786146c6c3c4f65622819b9
|
|
BLAKE2b-256 checksum How to use checksums |
b6ee10e031ad43a87d94dd0b068d6615330a6ec122293d02fa539c1e71bfa853
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp313-cp313-win_amd64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f1c1dca2b8d5a2bfce42c9da7a02ac5aeea89535fc67e533b5451fa7e7f7bd1c
|
|
BLAKE2b-256 checksum How to use checksums |
696792baf17d6e2a012bb22033931795fcf7261aad6e7b68f58da3907d016613
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp313-cp313-manylinux_2_34_aarch64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp313-cp313-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.13 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
96b66a0103a259ae683b73cecde0645d9e90fccacb621a65f04dcb4dc6a31367
|
|
BLAKE2b-256 checksum How to use checksums |
c9f3d0b7f08c9e969d78b917c16d0dbb94045c06fadbc6d0ad41bcc73b74bcb5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
190a12b52602930340f4867523f507d7a77b207e2965d796720a8ccde0fd2290
|
|
BLAKE2b-256 checksum How to use checksums |
c796e62f9c1a60813f89bfbf85ad11a39dc916b3b19dec376338877231a6e854
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2eb918464eb8fa2207c34e7c1f3b6aaf52bf4c4b2278217afc4628038c457fbc
|
|
BLAKE2b-256 checksum How to use checksums |
eceb4a6b821debc522225d21f3cd3d29c2abdfe1f80fccd778340ef0313d3923
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp313-cp313-macosx_10_12_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp313-cp313-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.13 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
cd2a701114b20d1085b0278c0d0f107c7c06885ea2d350bcc9620fed2c7720ce
|
|
BLAKE2b-256 checksum How to use checksums |
04729fed2b486b913747a7e852250c9ada66066e200cd3c5855defe9c3cf8d1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp312-cp312-win_amd64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8496ab6c90f73923391dd262cc627ee61dc5c973b1e4cdbb10e457e713a4131b
|
|
BLAKE2b-256 checksum How to use checksums |
0f14568d0f29a30f07fb0a2c062d5d9067db458f8be16c94dd1477d6d82b7d29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp312-cp312-manylinux_2_34_aarch64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp312-cp312-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.12 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
88b8b70ecf051d2e21a0debabb437b323fff211d565354aa80f48c8fc2d80d2e
|
|
BLAKE2b-256 checksum How to use checksums |
5101466b27e610c08649c269bcf7bc7cec6c17139832e42ef8fd9c74a7a3455a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
727a2eb3df27197efd1da6be202a40c74eb5815893c3cf7e6b06707dccb4d7d6
|
|
BLAKE2b-256 checksum How to use checksums |
e63ba8071ce52754501a1f43d1c63c7d79fe73bc5fd6665425883c1d6c632553
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9f8827fb39bb67d8a03925d1b1ff86cc3a00cbad7295730ccdadc13655afdbd0
|
|
BLAKE2b-256 checksum How to use checksums |
7a4baaca9e7ab9ff0bc185dc1f5da7b4408ce124298548351ba5999f807e5d18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp312-cp312-macosx_10_12_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp312-cp312-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.12 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
a0a1191f21278b69cbd55534f4c0b47fc97137545bdba704a32d412d31e6600d
|
|
BLAKE2b-256 checksum How to use checksums |
74342725aeae451fb62364d3b7a54fb071e26cde630b4063b89851161c441d3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp311-cp311-win_amd64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7e36e508ec450815a48ebc2124b4ec08b75b2cd71b700d27b4ad6d5cb38f73fc
|
|
BLAKE2b-256 checksum How to use checksums |
6d1bdbfa0dddf094b519fb1d4b15ed0f4fb4fa1a93346348c221315fe3b8d16e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp311-cp311-manylinux_2_34_aarch64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp311-cp311-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
53f12005d804ca4319dbd11c61aa26d00ae6069cb304978a2417424e293eaa26
|
|
BLAKE2b-256 checksum How to use checksums |
a06c057ecde6fa53959ddcb0ccf0b74906950b1e2c9a9e1dede1f81d52964363
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
b078b4b7411b184a3197fb78197adc41d14f3769387a724b434075d6b904009d
|
|
BLAKE2b-256 checksum How to use checksums |
1719b2c99b27199fda41db4e2ad6f0bbd78c8063bfd5a89d43faa92aa5c06121
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
271d77f85cf1a643b5506d9455796aa47ab2cbb68c3b33882961385bcbe7aea8
|
|
BLAKE2b-256 checksum How to use checksums |
617e1ba761b6734cc14c9424aef940380304887eda795a1d2cb2461710e16712
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp311-cp311-macosx_10_12_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp311-cp311-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
6043673d86f40c89a7931211a1b17072a05bafd8b6f4570951c29375a3beaa46
|
|
BLAKE2b-256 checksum How to use checksums |
75dc2f09562d5ceb30313a27b5349d9c61200b2cc283f4b92960d98165ee4be2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp310-cp310-manylinux_2_34_aarch64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp310-cp310-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.10 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
a7d70cae51211a33e813e2ae73acfc81ab7ed392b9fc5877a38817df615a3497
|
|
BLAKE2b-256 checksum How to use checksums |
95245828bf9d8774a4bde29724b1977c81b49bc25e8ea593e6b0a71610240571
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / rtest_forked_constants-0.0.48rc10-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rtest_forked_constants-0.0.48rc10-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
ae9000400f81f8468521a7d5b82f54b4ad53d872b46a025aafcb06c5caaee22f
|
|
BLAKE2b-256 checksum How to use checksums |
4601748267faf4425504499fb2d4a86dc3bbc18a66071d3b2a9fb3e173318e7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for rtest-forked-constants 0.0.48rc10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 31 files in this release have been uploaded with provenance metadata.
Attestation for rtest_forked_constants-0.0.48rc10.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
