pip-ascent
A versatile tool for effortlessly updating pip requirements while keeping your requirements.txt file in sync with the latest package versions. No more tedious manual package-by-package upgrades; this tool handles it for you and updates your requirements.txt file accordingly.
Purpose
This command-line tool allows you to interactively (or non-interactively) upgrade packages from your requirements file. It also enables you to update the pinned version in your requirements file(s). If no requirements are specified, the tool will attempt to detect the requirements file(s) in the current directory.
Installation
pip install pip-ascent
Note: This package installs the following dependencies: 'docopt', 'packaging', 'requests', 'terminaltables', 'colorclass'. To avoid installing these dependencies in your project, you can install pip-ascent in your system rather than your virtual environment. If you install it in your system and need to upgrade it, run pip install -U pip-ascent.
Usage
pip-ascent [<requirements_file>] ... [--prerelease] [-pk=<package>...] [--dry-run] [--check-greater-equal] [--skip-virtualenv-check] [--skip-package-installation] [--use-default-index]
Activate your virtual environment (important because it will also install the new versions of upgraded packages in the current virtual environment).
Change directory into your project. Then:
$ pip-ascent
Arguments:
requirements_file: Specifies the requirement file or uses a wildcard path to multiple files.--prerelease: Includes prerelease versions for upgrades when querying PyPI repositories.-pk <package>: Pre-selects packages for an upgrade, bypassing any prompts. You can also utilize regular expressions to filter packages for upgrading.--dry-run: Simulates the upgrade but does not perform the actual upgrade.--check-greater-equal: Also checks packages with minimum version pinning (package>=version).--skip-package-installation: Upgrades the version in requirement files only; it does not install the new package.--skip-virtualenv-check: Disables virtual environment check, permitting the installation of new packages outside the virtual environment.--use-default-index: Skips searching for a custom index URL in pip configuration file(s).
Examples:
-
pip-ascent: Automatically discovers the requirements file. -
pip-ascent requirements.txt -
pip-ascent requirements/dev.txt requirements/production.txt -
pip-ascent requirements.txt -pk django -pk celery -
pip-ascent requirements.txt -pk all -
pip-ascent requirements.txt --dry-run: Runs everything as a simulation (does not perform the actual upgrade)
💖 Like this project?
Leave a ⭐ if you find this project cool.
👨💻 Author
Abdulazeez Sherif
🍁 License
MIT
Note: This package is just starting out feel free to make contributions.
Metadata
Release files for pip-ascent 0.1.2
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_ascent-0.1.2.tar.gz | 16.1 kB | Without provenance | Details for pip_ascent-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pip_ascent-0.1.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for pip_ascent-0.1.2-py2.py3-none-any.whl |
Total release size: 39.1 kB
Release files / pip_ascent-0.1.2.tar.gz
| Download URL | pip_ascent-0.1.2.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6b0397f161d1f21f9f6b8cd9c084850dc276cca6526ae00d9f23e2bd3813418
|
|
BLAKE2b-256 checksum How to use checksums |
fa81badcc4e60b2c81ec6fbf8a5a7dc7619f08ad96aa64b554a1ec35d9c42b6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / pip_ascent-0.1.2-py2.py3-none-any.whl
| Download URL | pip_ascent-0.1.2-py2.py3-none-any.whl |
|---|---|
| Size | 23.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
643df52c31ee6dc94015a1827cef02a65a5815da0fe8f250ce5c6233aaef9cff
|
|
BLAKE2b-256 checksum How to use checksums |
7b5bd6e5c5bfb2a6e7fa513d7834616ea9e5d87b0e5d1b0a0848f1766af6e2de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for pip-ascent 0.1.2
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.