pyrig-fixtures
A pyrig plugin that provides pytest fixtures support.
Overview
pyrig-fixtures is a pyrig plugin that provides a library of reusable pytest fixtures for testing pyrig projects. Its fixtures — and any contributed by packages that depend on it — are made available automatically in every project that installs it.
What it adds
- A fixture library — ready-made fixtures for common testing needs: temporary project trees, module and package creation, config-file testing, CLI-command assertions, and environment gating.
- Automatic, cross-package availability — fixtures are registered as a pytest plugin so they work without imports, and any installed package that depends on pyrig-fixtures contributes its own fixtures the same way.
- A scaffolding command —
pyrig-fixtures fixture <name>adds a new fixture stub to your project's shared fixtures module. - An end-to-end init check — an autouse fixture that builds this project,
initializes a fresh scratch project with it installed as a pyrig plugin via
pyrig init, and verifies everything works. Runs once per test session even under pytest-xdist. Skip it with the--skip-init-pyrig-projectpytest flag (--sippfor short).
Usage
uv add pyrig-fixtures --dev
uv run pyrig sync
Documentation
Full documentation, including the auto-generated API reference, is available on the documentation site.
1 maintainer
Metadata
1 maintainer
Release files for pyrig-fixtures 2.26.18
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 | |
|---|---|---|---|---|
| pyrig_fixtures-2.26.18.tar.gz | 15.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyrig_fixtures-2.26.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.6 kB
Release files / pyrig_fixtures-2.26.18.tar.gz
| Download URL | pyrig_fixtures-2.26.18.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8dc5bbd8a1c4a33ec32da53367477c75d63f3ccafcdec5e2731cf68e38a2214d
|
|
BLAKE2b-256 checksum How to use checksums |
774c4411a431a19a176014da4ea984c20a81efd1cbfb5a3bf7456fb51dcfb6fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / pyrig_fixtures-2.26.18-py3-none-any.whl
| Download URL | pyrig_fixtures-2.26.18-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6824129e26c1b8fc3b941dbeb41bf8d87d264fb64e75d77c3b7cd7d57073ce87
|
|
BLAKE2b-256 checksum How to use checksums |
0bcfec80a57e3a41ffdfff32f6ac12f873b451c61b90e68f5b9badd31b333317
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for pyrig-fixtures 2.26.18
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
