Crates.io | update-pypi-deps |
lib.rs | update-pypi-deps |
version | 0.1.0 |
source | src |
created_at | 2024-06-10 09:54:33.324229 |
updated_at | 2024-06-10 09:54:33.324229 |
description | Parse pypi dependencies from pyproject.toml and output the latest versions |
homepage | |
repository | https://github.com/Nathan Henrie/update-pypi-deps |
max_upload_size | |
id | 1266913 |
size | 398,972 |
Parse pypi dependencies from pyproject.toml and output the latest versions
NB: This is a low-investment toy / hobby project.
pyproject.toml
dependencies
and optional-dependencies
Sometimes I want to update all of a python's project top-level dependencies to the latest version and see if it still works. If so, I commit the change. If not, I try to sort out which of the dependencies are holding me back and why. Most sane people will just use something like poetry or pip-tools, but after getting burned by investing time to learn Pipenv, I now prefer to do it the old fashioned way.
$ update-pypi-deps [ -i /path/to/pyproject.toml ]
cargo install update-pypi-deps
$ nix run github:n8henrie/update-pypi-deps
fauxmo>0.1,<0.6
); it just reuses the same contraint it is given, but with a
new version number