Update Python Project Dependencies (UPPD)
Update dependencies and optional dependencies in pyproject.toml files based on defined match operators.
This project aims to enable a similar workflow as pur does for requirements.txt files.
Getting Started
Install and run:
pip install uppd uppd INFO: dlister==1.1.0 -> dlister==1.2.0 INFO: pytest-aiohttp==1.0.0 -> pytest-aiohttp==1.0.5 INFO: pytest==8.0.0 -> pytest==8.3.3
Set inputs and output files:
uppd -i dev/pyproject.toml uppd -i pyproject.toml -o pyproject.toml.updated
Skip dependencies:
uppd --skip foo bar
Allow upgrade to pre releases:
uppd --pre foo bar
Print help:
uppd --help
usage: uppd [-h]
[-i INFILE]
[-o OUTFILE]
[-m [{<,<=,==,>=,>,~=} ...]]
[--skip [SKIP ...]]
[--dev [DEV ...]]
[--pre [PRE ...]]
[--post [POST ...]]
[--index-url INDEX_URL]
[--log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}]
[--log-file LOG_FILE]
[--dry-run]
[-v]
Update Python Project Dependencies.
options:
-h, --help show this help message and exit
-i INFILE, --infile INFILE
path(s) to input file(s) (default: pyproject.toml)
-o OUTFILE, --outfile OUTFILE
path(s) to output file(s). (default: [])
-m [{<,<=,==,>=,>,~=} ...], --match-operators [{<,<=,==,>=,>,~=} ...]
operators to upgrade. (default: ['==', '<=', '~='])
--skip [SKIP ...] dependencies to skip upgrade. (default: [])
--dev [DEV ...] dependencies to upgrade to dev release. (default: [])
--pre [PRE ...] dependencies to upgrade to pre release. (default: [])
--post [POST ...] dependencies to upgrade to post release. (default: ['*'])
--index-url INDEX_URL
base URL of the Python Package Index. (default: https://pypi.org)
--log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}
logging level. (default: INFO)
--log-file LOG_FILE pipe loggining to file instead of stdout. (default: None)
--dry-run do not save changes to output file(s). (default: False)
-v, --version show program's version number and exit
The following settings (with defaults) can be set/overwritten in the infile:
[tool.uppd] match_operators = ["==", "<=", "~="] skip = [] dev = [] pre = [] post = ["*"] index_url = "https://pypi.org"
Development
Setup, run tests and release:
pip install -e .[dev] brundle pytest bouillon release
Credits
This project aims to enable a similar workflow as pur for requirements.txt files, and essentially exists because pur (at the time of writing) does not support upgrading dependencies in pyproject.toml files.
Metadata
Release files for uppd 1.6.0
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 | |
|---|---|---|---|---|
| uppd-1.6.0.tar.gz | 11.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uppd-1.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.3 kB
Release files / uppd-1.6.0.tar.gz
| Download URL | uppd-1.6.0.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa87c53b24378e460dfe0fdb861f167346a5321c0a513fabb6c77bc019625105
|
|
BLAKE2b-256 checksum How to use checksums |
e8b0954358eca5e86935eaf75d2d3cb2bdddd5429884105b7fbeeb2302b5cc1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / uppd-1.6.0-py3-none-any.whl
| Download URL | uppd-1.6.0-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e0fbd3945609e6342d3586ce50157946b19c933cecec6cce31870bbc20307f6e
|
|
BLAKE2b-256 checksum How to use checksums |
c1f285158a1786709ec73992c66804348fca5a6e5b643e3a66581dfbbec525ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for uppd 1.6.0
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.