cot.tmppath
A hardened, fast building block for related temporary folders: one folder per run, items side by side inside it, kept or removed by policy, safe with concurrent processes. For test runners (a pytest binding) and for cot.runsomewhere's bootstrap staging and worker scratch.
Early. The goals are in docs/goals.md, the background in
docs/research.md, and testing/ states the goals as
tests. How the core keeps them is in docs/core.md.
uv run pytest -q
uv run mypy
uv run --group bench pytest benchmarks
pytest projects can opt in to having pytest's tmp_path and
tmp_path_factory replaced. The py.path fixtures tmpdir and
tmpdir_factory are not provided:
[pytest]
addopts = -p cot.tmppath.overtake_pytest
How and why is in docs/pytest-replacement.md.
Old runs can be removed by hand; it lists them and asks before removing:
python -m cot.tmppath prune --all-projects --older-than 7d
1 maintainer
Metadata
1 maintainer
Release files for cot.tmppath 0.2.1
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_tmppath-0.2.1.tar.gz | 78.1 kB | With provenance | Details for cot_tmppath-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cot_tmppath-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for cot_tmppath-0.2.1-py3-none-any.whl |
Total release size: 97.9 kB
Release files / cot_tmppath-0.2.1.tar.gz
| Download URL | cot_tmppath-0.2.1.tar.gz |
|---|---|
| Size | 78.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc0b013faa687d2944225cf39731c927bb7a597553eaa157cabfb3e582e07261
|
|
BLAKE2b-256 checksum How to use checksums |
d9a7e851e6f3220901a06772dceb8b8114733669c0191b149be9c787402918ea
|
| 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_tmppath-0.2.1-py3-none-any.whl
| Download URL | cot_tmppath-0.2.1-py3-none-any.whl |
|---|---|
| Size | 19.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af803320dcbf7a2266e1792264bb8d56cdcd2024bc95671ddfe2a8062409914b
|
|
BLAKE2b-256 checksum How to use checksums |
976e35e86b0b52c048666a1c841362380df30c8eea5bafd2fe52c6c46862a9be
|
| 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.tmppath 0.2.1
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_tmppath-0.2.1.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.
