cot.pytest
pytest, with its parts replaced by the cogs-of-testing versions.
cot-pytest [pytest arguments]
python -m cot.pytest [pytest arguments]
cot-pytest runs pytest.main with every usable replacement switched on in
front of your arguments, and names in the header which part runs whose code:
| Part | Replaced by | Status |
|---|---|---|
| assertion rewriting | cot-assert (-p cot_assert --cot-assert) |
on |
tmp_path and tmp_path_factory (tmpdir and tmpdir_factory are not provided) |
cot.tmppath (-p cot.tmppath.overtake_pytest) |
on |
| output capture | cot.capture (-p cot.capture.overtake_pytest) |
on |
A part that is off leaves pytest's builtin in place. The parts are declared
in src/cot/pytest/_parts.py.
Pre-alpha, not released.
uv run pytest -q
uv run mypy
pre-commit run -a
1 maintainer
Metadata
1 maintainer
Release files for cot-pytest 0.1.0
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 |
|---|---|---|---|---|
| cot_pytest-0.1.0.tar.gz | 41.4 kB | With provenance | Details for cot_pytest-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cot_pytest-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for cot_pytest-0.1.0-py3-none-any.whl |
Total release size: 46.2 kB
Release files / cot_pytest-0.1.0.tar.gz
| Download URL | cot_pytest-0.1.0.tar.gz |
|---|---|
| Size | 41.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fdf9203b33856f67b1c9a2e20fc5e84c0f20b0bfccfdb8c2293004ebf016e03a
|
|
BLAKE2b-256 checksum How to use checksums |
8fe2f134914f2bdf368a943641da6dd78958149bded3a68e63efe311f9896614
|
| 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 8, 2026.
Transparency logRelease files / cot_pytest-0.1.0-py3-none-any.whl
| Download URL | cot_pytest-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e0a9be29ff69283874e8146097b45d97b30db47734c1c60cd61d4c7594d80c9
|
|
BLAKE2b-256 checksum How to use checksums |
b32710fea3eb3f70bfd3a9f3e60c98f2c7277f9715a1c392dcb0b0d83359ae54
|
| 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 8, 2026.
Transparency logSecurity for cot-pytest 0.1.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for cot_pytest-0.1.0.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 8, 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.
