extremal-python-dependencies
A utility for installing extremal versions of dependencies for more robust testing.
Install extremal versions of package dependencies for more robust continuous integration testing, given a package that specifies its dependencies in a pyproject.toml file.
For instance, one might use this utility to install the minimum supported version of each dependency before a CI run. Ensuring all tests then pass adds confidence that the code is indeed compatible with the full range of package versions it claims to be compatible with, helping to prevent users from encountering broken installs.
Another way to use this tool is to install development versions of certain packages.
This utility works with dependencies specified in a pyproject.toml file. It modifies pyproject.toml, either by sending the transformed version to stdout (the default) or by modifying in place (which may be useful in CI scripts).
How to use
The following snippet modifies pyproject.toml in place to test with the minimum supported version of each direct dependency, under the minimum supported tox version (as specified by minversion in tox.ini).
pip install "tox==$(extremal-python-dependencies get-tox-minversion)"
extremal-python-dependencies pin-dependencies-to-minimum --inplace
tox -epy
The following snippet modifies pyproject.toml in place to test with the development version of one or more dependencies:
extremal-python-dependencies pin-dependencies \
"qiskit @ git+https://github.com/Qiskit/qiskit.git" \
"qiskit-ibm-runtime @ git+https://github.com/Qiskit/qiskit-ibm-runtime.git" \
--inplace
tox -epy
Each of the above patterns can be used in a CI script.
Caveats
- The minimum versions of all optional dependencies installed simultaneously must be compatible with each other.
- This tool does not set the minimum supported version of transitive dependencies.
Similar tools
- requirements-builder: builds requirements from a
setup.pyfile instead of apyproject.tomlfile - uv's
--resolutionstrategies:lowest-directinstalls the lowest compatible versions of direct dependencies (similar to thepin-dependenciespattern above), whilelowestextends this to transitive dependencies as well — addressing a caveat of this tool. Ifextremal-python-dependenciesdoes not meet your needs,uvmay.
Metadata
Release files for extremal-python-dependencies 1.0.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 | |
|---|---|---|---|
| extremal_python_dependencies-1.0.0.tar.gz | 14.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| extremal_python_dependencies-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.1 kB
Release files / extremal_python_dependencies-1.0.0.tar.gz
| Download URL | extremal_python_dependencies-1.0.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c22334908e8707ef9b7e75b528c4eacc1c890417dc32d14b7b0265415b227df4
|
|
BLAKE2b-256 checksum How to use checksums |
26bc3a9c92a3ca9d589e5fee5d30de901a9b57c95bfaee4a5b2f201ca794c018
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 9, 2026.
Transparency logRelease files / extremal_python_dependencies-1.0.0-py3-none-any.whl
| Download URL | extremal_python_dependencies-1.0.0-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cf2db865ea0590711026620efac15dd8c40408463eb542ed3f316a2c6024b25b
|
|
BLAKE2b-256 checksum How to use checksums |
08b9956ea28d98b5405b0619f23e297461ec657080f1209c0290cac4cb1dafce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 9, 2026.
Transparency log