Pip Requ
A set of command line tools to help you keep your pip-based packages fresh, even when you’ve pinned them. You do pin them, right?
Pip Requ is a fork of pip-tools by Vincent Driessen.
Installation
$ pip install --upgrade pip # Pip Requ needs pip==8.0 or higher
$ pip install pip-requ
Example usage for pip-requ compile
Suppose you have a Flask project, and want to pin it for production. Write the following line to a file:
# requirements.in
Flask
Now, run pip-requ compile requirements.in:
$ pip-requ compile requirements.in
#
# This file is autogenerated by pip-requ compile
# Make changes in requirements.in, then run this to update:
#
# pip-requ compile requirements.in
#
flask==0.10.1
itsdangerous==0.24 # via flask
jinja2==2.7.3 # via flask
markupsafe==0.23 # via jinja2
werkzeug==0.10.4 # via flask
And it will produce your requirements.txt, with all the Flask dependencies (and all underlying dependencies) pinned. Put this file under version control as well.
To update all packages, periodically re-run pip-requ compile --upgrade.
To update a specific package to the latest or a specific version use the --upgrade-package or -P flag:
pip-requ compile --upgrade-package flask
# only update the flask package
pip-requ compile --upgrade-package flask --upgrade-package requests
# update both the flask and requests packages
pip-requ compile -P flask -P requests==2.0.0
# update the flask package to the latest, and requests to v2.0.0
Example usage for pip-requ sync
Now that you have a requirements.txt, you can use pip-requ sync to update your virtual env to reflect exactly what’s in there. Note: this will install/upgrade/uninstall everything necessary to match the requirements.txt contents.
$ pip-requ sync
Uninstalling flake8-2.4.1:
Successfully uninstalled flake8-2.4.1
Collecting click==4.1
Downloading click-4.1-py2.py3-none-any.whl (62kB)
100% |████████████████████████████████| 65kB 1.8MB/s
Found existing installation: click 4.0
Uninstalling click-4.0:
Successfully uninstalled click-4.0
Successfully installed click-4.1
To sync multiple *.txt dependency lists, just pass them in via command line arguments e.g.:
$ pip-requ sync dev-requirements.txt requirements.txt
Passing in empty arguments would cause it to default to requirements.txt.
Metadata
Release files for pip-requ 0.180.7
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 |
|---|---|---|---|---|
| pip-requ-0.180.7.tar.gz | 30.0 kB | Without provenance | Details for pip-requ-0.180.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pip_requ-0.180.7-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for pip_requ-0.180.7-py2.py3-none-any.whl |
Total release size: 71.4 kB
Release files / pip-requ-0.180.7.tar.gz
| Download URL | pip-requ-0.180.7.tar.gz |
|---|---|
| Size | 30.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f7e9f5fe3d5b36ebeb394ebdeeff2c1bc565cdaa1ad16d9a0d58695d5cbb6cd
|
|
BLAKE2b-256 checksum How to use checksums |
11b2230856630444cf2edc70edeb8fb6917f5ef2706dcbcfd660e75656ed1812
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pip_requ-0.180.7-py2.py3-none-any.whl
| Download URL | pip_requ-0.180.7-py2.py3-none-any.whl |
|---|---|
| Size | 41.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a959545deaf5dd75a175cf221df7cef06d3834da289cc1d904a32dcfbff53dfa
|
|
BLAKE2b-256 checksum How to use checksums |
06188ca9548477cf2a5ab4ca76940d46244461c5674a0b13ee0454610817211e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pip-requ 0.180.7
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.