luddite
luddite checks if pinned versions in your requirements.txt file have newer versions in the package index. It’s great to be near the cutting edge, but not so close that you get cut! This tool will help you keep things up to date manually.
There are many ways to specify requirements in those files, but luddite’s parsing is pretty dumb and simple: we’re only looking for package==version pins. It won’t break on lines that aren’t fitting this format, but you’ll have to check them manually.
luddite works on both Python 2 and Python 3.
Installation
pip install luddite
Usage
luddite /path/to/requirements.txt
If you are in the same directory as the requirements.txt file, you can just type luddite.
Example output
1 maintainer
Metadata
1 maintainer
Release files for luddite 1.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 | Actions |
|---|---|---|---|---|
| luddite-1.0.4.tar.gz | 9.6 kB | Without provenance | Details for luddite-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| luddite-1.0.4-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for luddite-1.0.4-py2.py3-none-any.whl |
Total release size: 19.4 kB
Release files / luddite-1.0.4.tar.gz
| Download URL | luddite-1.0.4.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e05001efc80eb6c1c7514439812fbc71a66d59e031e09f9a72772f3e6cddfab7
|
|
BLAKE2b-256 checksum How to use checksums |
9e9323defe449b102db8744ea89984aafb4b10df7f91ddabc73ecae07ef13a6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Release files / luddite-1.0.4-py2.py3-none-any.whl
| Download URL | luddite-1.0.4-py2.py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
dfc8591d11954731f0d466eb9e89cbefdeccf7f1e076c38dc8631dea6f2f7a58
|
|
BLAKE2b-256 checksum How to use checksums |
390849095063da78a5b4159ba71ae95d595f5065e351e5f2b998c0b688888e74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for luddite 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
