pip_upgrade_outdated
Run pip install --upgrade for all outdated packages (pip list --outdated).
Allow specifying which version of pip to run, and parallel or serial execution of the upgrade step.
Command line usage
usage: pip_upgrade_outdated [-h] [-3 | -2 | --pip_cmd PIP_CMD]
[--serial | --parallel]
[--sequential_run | --batch_run] [--user]
[--dry_run] [--verbose] [--version]
[--exclude PKG]
Upgrade outdated python packages with pip. Any unknown arguments will be passed to pip.
optional arguments:
-h, --help show this help message and exit
-3 use pip3
-2 use pip2
--pip_cmd PIP_CMD use PIP_CMD (default pip)
--serial, -s upgrade in serial via a single pip upgrade command (default)
--parallel, -p upgrade in parallel via individual pip upgrade commands
--sequential, -q upgrade in serial via individual pip upgrade commands
--user, -u Adds the --user flag when installing the packages
--dry_run, -n get list, but don't upgrade
--verbose, -v may be specified multiple times
--version show program's version number and exit
--exclude PKG, -x PKG
exclude PKG; may be specified multiple times
TODO
- Need better error handling?
- Should the script explicitly return a value to the shell?
- allow patterns in exclude option
Sources
- code based on https://gist.github.com/serafeimgr/b4ca5d0de63950cc5349d4802d22f3f0
- project structure based on https://gehrcke.de/2014/02/distributing-a-python-command-line-application/
Metadata
Release files for pip-upgrade-outdated 1.5
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_upgrade_outdated-1.5.tar.gz | 5.0 kB | Without provenance | Details for pip_upgrade_outdated-1.5.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pip_upgrade_outdated-1.5-py3-none-any.whl | Python 3 | none | any | Details for pip_upgrade_outdated-1.5-py3-none-any.whl |
| pip_upgrade_outdated-1.5-py2-none-any.whl | Python 2 | none | any | Details for pip_upgrade_outdated-1.5-py2-none-any.whl |
Total release size: 17.2 kB
Release files / pip_upgrade_outdated-1.5.tar.gz
| Download URL | pip_upgrade_outdated-1.5.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2486baf85ca80d92c2e3483ef71ff7c971f2dea73ab3fad300c2cf29283f01e3
|
|
BLAKE2b-256 checksum How to use checksums |
b3c3d0a855d3b904b8b5eb373659ff8c293bafc0fe952ae389025d123e6b49ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.7.1
|
Release files / pip_upgrade_outdated-1.5-py3-none-any.whl
| Download URL | pip_upgrade_outdated-1.5-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86cbe75bead77725633cdb28e4db2f9be113a5620dc645b0a03898c5cf425b17
|
|
BLAKE2b-256 checksum How to use checksums |
7e723f16cf49f59ceb57af56ab01861ed6c49f5b96d875c4827e5e8d19acf467
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.7.1
|
Release files / pip_upgrade_outdated-1.5-py2-none-any.whl
| Download URL | pip_upgrade_outdated-1.5-py2-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
d32dadabb342bd30e00d6c3d6e0af9e6f7bf22db582dc3bb57d478c8dffd7d92
|
|
BLAKE2b-256 checksum How to use checksums |
8345b30e13dab93dc5c34107bb00e179c6dafc65306a89b10c5cae7b267909fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.7.1
|
Security for pip-upgrade-outdated 1.5
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.