A PEP 517 build backend that automatically adds requirements.txt contents to wheel dependencies.
Usage
Use setup_requirements as your build backend in pyproject.toml:
[build-system] requires = ['setuptools>=42', 'wheel', 'setup-requirements'] build-backend = 'setup_requirements'
Notes
This backend should be used if you want to build an application with pinned dependencies. For libraries use standard install_requires without pins.
The backend exists only because it’s not possible to use file: in install_requires (yet?). See this github issue.
Limitations
It’s not possible to use a different path than a top-level requirements.txt file.
1 maintainer
Metadata
1 maintainer
Release files for setup-requirements 1.2
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 | |
|---|---|---|---|---|
| setup_requirements-1.2.tar.gz | 5.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| setup_requirements-1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.5 kB
Release files / setup_requirements-1.2.tar.gz
| Download URL | setup_requirements-1.2.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a4bae3780cc468f84e01b6b12dd253ebdbc5ac4b1f221e14b690ca7c9ccddfa
|
|
BLAKE2b-256 checksum How to use checksums |
a49a09459380231f622a25e6222a9af8c18f2fee418174ea4188e8f30a0bf033
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.4
|
Release files / setup_requirements-1.2-py3-none-any.whl
| Download URL | setup_requirements-1.2-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
829d1589e4b170009d3f50543254880ed399edfa01d24d8c894db8a8faaa7fa2
|
|
BLAKE2b-256 checksum How to use checksums |
2371db6e7d9bea6a8e11644ec09e6fc65f6c3daa712c831d5326a71f57ab04f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.4
|
Security for setup-requirements 1.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
