pypiece
Wrapper around pip for use with flaky connections.
Basic idea behind it is that default behaviour of pip to download all packages at once and compile them can get pretty frustrating in situations, where single error in downloading or installing a package can result in repeating whole process all over again.
pypiece tries to get around that by trying to download and install each package separately, by calling pip for each line of requirements.txt. In the end it outputs list of successfully installed packages and ones that failed.
Usage
pypiece < requirements file > < – PIP options >
Available options:
–pip - specify pip binary to use
–retries <N> - try to reinstall failing package _N_ times (default: 3).
–venv <name> - install to virtualenvwrapper created virtual environment _name_.
pip arguments
If – is found in command line, then all arguments after it will be passed unchanged to pip executable on every call.
For example:
pypiece requirements.txt – -i https://my.pypi.repo
Last line is equivalent to:
pip install -r requirements.txt -i https://my.pypi.repo
Examples
Try to install every package found in _requirements.txt_ one by one:
pypiece requirements.txt
Install requirements using pip from virtualenv _test_:
pypiece –venv test requirements.txt
Install requirements using specified pip binary:
pypiece –pip my_env/bin/pip requirements.txt
Feedback
Send your bug reports and suggestions to [lensvol@gmail.com][1]
1 maintainer
Metadata
1 maintainer
Release files for pypiece 0.1.3.1
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 |
|---|---|---|---|---|
| pypiece-0.1.3.1.tar.gz | 3.4 kB | Without provenance | Details for pypiece-0.1.3.1.tar.gz |
Release files / pypiece-0.1.3.1.tar.gz
| Download URL | pypiece-0.1.3.1.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8224b9cb4c4a87411d815d2d192f793dd47d92a46b367fcab4b97ca79b85c4e9
|
|
BLAKE2b-256 checksum How to use checksums |
36ae602ecee557560827b69e69111865181b2e74e9843e7697d7651477318ffc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pypiece 0.1.3.1
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.
