pip-update-requirements
Update the packages in a requirements.txt file.
Installation
pip install pur
Usage
Give pur your requirements.txt file and it updates all your packages to the latest versions.
For example, given a requirements.txt file:
flask==0.9 sqlalchemy==0.9.10 alembic==0.8.4
Running pur on that file updates the packages to current latest versions:
$ pur -r requirements.txt Updated flask: 0.9 -> 0.10.1 Updated sqlalchemy: 0.9.10 -> 1.0.12 Updated alembic: 0.8.4 -> 0.8.6 All requirements up-to-date.
Pur never modifies your environment or installed packages, it only modifies your requirements.txt file.
Options
- -r, --requirement PATH
The requirements.txt file to update; Defaults to using requirements.txt from the current directory if it exist.
- -o, --output PATH
Output updated packages to this file; Defaults to overwriting the input requirements.txt file.
- -f, --force
Force updating packages even when a package has no version specified in the input requirements.txt file.
- -d, --dry-run
Output changes to STDOUT instead of overwriting the requirements.txt file.
- -s, --skip TEXT
Comma separated list of packages to skip updating.
- -z, --nonzero-exit-code
Exit with status l0 when all packages up-to-date, 11 when some packages were updated. Defaults to exit status zero on success and non-zero on failure.
- --version
Show the version and exit.
- --help
Show this message and exit.
Contributing
Before contributing a pull request, make sure tests pass:
virtualenv venv . venv/bin/activate pip install tox tox
Many thanks to all contributors!
1 maintainer
Metadata
1 maintainer
Release files for pur 3.0.6
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 | |
|---|---|---|---|---|
| pur-3.0.6.tar.gz | 903.0 kB | Without provenance | Details |
Release files / pur-3.0.6.tar.gz
| Download URL | pur-3.0.6.tar.gz |
|---|---|
| Size | 903.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
124fad9b3dc8990bd960c66b02012176b4e5187927340694ec23e56d161e1198
|
|
BLAKE2b-256 checksum How to use checksums |
67b5afdd5f3475b6629c0e0700edf140811567a19530cc0998ee3000ddfe4752
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pur 3.0.6
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.
