Dlister
Print or save to a file, dependencies in a pyproject.toml file based on defined match operators. This is similar to a dependency ‘freeze’ but with added configurability.
This can be useful for finding and testing with the oldest versions of the dependencies for which support is declared in pyproject.toml.
Getting Started
Install and run:
pip install dlister
dlister --help
usage: dlister [-h]
[-i INFILE]
[-o OUTPUT]
[-m [{<,<=,==,>=,>,~=} ...]]
[--skip [SKIP ...]]
[--log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}]
[--log-file LOG_FILE]
[-v]
[dependencies ...]
Print Python Project Dependencies.
positional arguments:
dependencies path(s) to input file(s) (default: [])
options:
-h, --help show this help message and exit
-i INFILE, --infile INFILE
path(s) to input file(s) (default: pyproject.toml)
-o OUTPUT, --output OUTPUT
output file. (default: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>)
-m [{<,<=,==,>=,>,~=} ...], --match-operators [{<,<=,==,>=,>,~=} ...]
operators to upgrade. (default: ['==', '>='])
--skip [SKIP ...] dependencies to skip. (default: [])
--log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}
logging level. (default: WARNING)
--log-file LOG_FILE pipe loggining to file instead of stdout. (default: None)
-v, --version show program's version number and exit
Usage
Run:
dlister packaging==22.0 tomli==2.0.0; python_version < "3.11" dlister -m "<=" "==" packaging==24.1 tomli==2.0.2; python_version < "3.11" dlister test packaging==22.0 tomli==2.0.0; python_version < "3.11" brundle==1.1.0 isort==5.13.2 mypy==1.13.0 ruff==0.7.1 pytest==8.3.3 pytest-cov==5.0.0 dlister "*" packaging==22.0 tomli==2.0.0; python_version < "3.11" brundle==1.1.0 isort==5.13.2 mypy==1.13.0 ruff==0.7.1 pytest==8.3.3 pytest-cov==5.0.0 bouillon==2.6.0 build==1.2.2.post1 licensecheck==2024.3 uppd==1.3.0 twine==5.1.1 dlister test -o requirements.old
Development
Setup, run tests and release:
pip install .[dev] brundle pytest bouillon release 1.2.3
1 maintainer
Metadata
1 maintainer
Release files for dlister 1.3.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 | |
|---|---|---|---|---|
| dlister-1.3.0.tar.gz | 7.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dlister-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.2 kB
Release files / dlister-1.3.0.tar.gz
| Download URL | dlister-1.3.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c612d4ce183c27d804298ebcd6ed9573d16d9b949a5812838f5eeda336bf52f5
|
|
BLAKE2b-256 checksum How to use checksums |
69b02f732d483a51cec905f5ac1674770cda80d0551a6c9eb4c69f11b4ff5ba6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / dlister-1.3.0-py3-none-any.whl
| Download URL | dlister-1.3.0-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f3b69fa0e8d56a05ed66a94920f9424a8bbe9df43a7a6adb723a63913b30156
|
|
BLAKE2b-256 checksum How to use checksums |
599e906e3a6bac0761b24b5d2025aab3f56823c991a2722f9e1dc9d4626960ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for dlister 1.3.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.
