pinner
A tiny console script to verify you have pinned all of your python requirements.
Why you should specify exact version in requirements.txt
Example:
$ cat requirements.txt PIL coveralls>=1.0a1 responses==0.3.0 git+https://github.com/miracle2k/django-assets.git@master#egg=django_assets -e git+git://github.com/miracle2k/webassets.git@9956fb86c1c750672324b2c95c9a464a0ef11a4f#egg=webassets git+https://github.com/fcurella/django-recommends.git#egg=django_recommends $ pinner ./requirements.txt:1:1: R001 Dependency PIL not pinned ./requirements.txt:2:1: R002 Dependency coveralls should be pinned to exact version ./requirements.txt:4:1: R004 VCS dependency django_assets specifies branch/tag, commit expected ./requirements.txt:6:1: R003 VCS dependency django_recommends lacks revision specifier [4]
You can use it in your commit hook or CI tests
Changelog
0.1.0 (2015-03-01)
First release on PyPI
Metadata
Release files for pinner 1.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 | Provenance | Actions |
|---|---|---|---|---|
| pinner-1.0.tar.gz | 7.0 kB | Without provenance | Details for pinner-1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pinner-1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for pinner-1.0-py2.py3-none-any.whl |
Total release size: 12.8 kB
Release files / pinner-1.0.tar.gz
| Download URL | pinner-1.0.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b9ca976ff5f08574f881fe673dd972d01645304581e8979746733f131c0100b
|
|
BLAKE2b-256 checksum How to use checksums |
5d32f5c2fcc3cde929d14c2007551739cf13342de6b4c9e6cfe8d2f884e9cee5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pinner-1.0-py2.py3-none-any.whl
| Download URL | pinner-1.0-py2.py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f805c19fafdd20623d894f55383085b791f9de1516d160affd24d0cec356a0b0
|
|
BLAKE2b-256 checksum How to use checksums |
e0a735234126a60855016fb2c229fddc2d2255375a99fb4c990b1719827b6052
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pinner 1.0
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.