Pips
pip wrapper for new requirements handling
https://www.kennethreitz.org/essays/a-better-pip-workflow
pips install flask
- run pip install flask
- add flask to requirements.txt
- run pip freeze > requirements.lock
pips uninstall flask
- run pipdeptree
- run pip uninstall for all dependencies
- remove flask from requirements.txt
- run pip freeze > requirements.lock
pips install
- run pip install -r requirements.lock
pips update
- run pip install -r requirements.txt
- run pip freeze > requirements.lock
Setup Project
pip install requirements-dev.txt
Build and Deployment
python setup.py sdist bdist_wheel twine upload dist/*
Metadata
Release files for pips-tool 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 |
|---|---|---|---|---|
| pips-tool-0.4.tar.gz | 4.4 kB | Without provenance | Details for pips-tool-0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pips_tool-0.4-py3-none-any.whl | Python 3 | none | any | Details for pips_tool-0.4-py3-none-any.whl |
Total release size: 7.6 kB
Release files / pips-tool-0.4.tar.gz
| Download URL | pips-tool-0.4.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0f50a66176acebf27b08cf478c4ca1d90859a6a1270000596800369cf35b8120
|
|
BLAKE2b-256 checksum How to use checksums |
df267b34f48a50e161d25a14fca139f02eeafa29ce5e7af83c740a434c698834
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.3
|
Release files / pips_tool-0.4-py3-none-any.whl
| Download URL | pips_tool-0.4-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cfba3e0df6d003800b354bac8dff9d371fe9b63bc9a8be7603d7353660c7aa0d
|
|
BLAKE2b-256 checksum How to use checksums |
5809ece8e537e9897c13ab533de5c242833cdb9367619d7afbae7a4344f5f4a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.3
|
Security for pips-tool 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.