Pin your requirements.txt dependencies without adding new ones
Usage:
To install, pip install pinmyreqs
To use, pip freeze | pinmyreqs requirements.txt
There’s also an utility to unpin your deps so you can upgrade all of them:
unpinmyreqs requirements.txt
Alternatives:
1 maintainer
Metadata
1 maintainer
Release files for pinmyreqs 0.4
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 | |
|---|---|---|---|---|
| pinmyreqs-0.4.tar.gz | 1.9 kB | Without provenance | Details |
Release files / pinmyreqs-0.4.tar.gz
| Download URL | pinmyreqs-0.4.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0c4373e8714b79fdb93a375dbd8f34d09320b00596d67118cbbbaf19c1aec45
|
|
BLAKE2b-256 checksum How to use checksums |
59fbe1111b6064e339423e173cace21753ab600d5954dd1a11018f6a5912d2c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pinmyreqs 0.4
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.
