cot.capture
Building blocks for capturing output at different levels: Python's
sys.stdout/sys.stderr/sys.stdin slots and the process's file
descriptors, with proxies that are closed when their scope ends and say who
created them when misused afterwards.
Early, and not released. The design is in docs/design/streams.md; the research it starts from is docs/research.md.
pytest
cot.capture.overtake_pytest is an opt-in pytest plugin that captures test
output with cot.capture instead of pytest. Enable it per project:
[pytest]
addopts = -p cot.capture.overtake_pytest
--capture=fd (the default) and --capture=sys map to descriptor and slot
level; -s captures nothing; tee-sys is left to pytest. capsys, capfd
and pytest's capturemanager keep working. The module docstring lists what
differs from pytest's own capture.
1 maintainer
Metadata
1 maintainer
Release files for cot-capture 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_capture-0.1.0.tar.gz | 78.3 kB | With provenance | Details for cot_capture-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cot_capture-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for cot_capture-0.1.0-py3-none-any.whl |
Total release size: 94.5 kB
Release files / cot_capture-0.1.0.tar.gz
| Download URL | cot_capture-0.1.0.tar.gz |
|---|---|
| Size | 78.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10eb0fc771552cc4d99c6aa0aae08e896475d8c5545d21d665bf6cbdef44a6f3
|
|
BLAKE2b-256 checksum How to use checksums |
6fb44fb8026eee544ead99f5f3c4b716c2c07006f5d31a48ed5be5c1a54c0032
|
| 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 7, 2026.
Transparency logRelease files / cot_capture-0.1.0-py3-none-any.whl
| Download URL | cot_capture-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d526597ed16f676090bbdedda23bd29bb8f3932d993d934747b7048292079549
|
|
BLAKE2b-256 checksum How to use checksums |
2c810b61bccfba254dd61cf28528160ea59e929ff038f89f085e2087065c08f4
|
| 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 7, 2026.
Transparency logSecurity for cot-capture 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_capture-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 7, 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.
