-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
show outdated constraints #4175
Labels
Comments
jstriebel
added
kind/feature
Feature requests/implementations
status/triage
This issue needs to be triaged
labels
Jun 11, 2021
cf #4342 |
2 tasks
I think |
I agree. Its a pain to lookup what direct deps are outdated or not. |
1 task
2 tasks
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Feature Request
The version constraints in
pyproject.toml
are often used to prevent backwards-incompatible upgrades, e.g. the caret-notation for packages that follow semantic versioning. It would be helpful to get an overview of all constraints that prevent to install the newest available version of the package. An example:I installed
some_package
with the^3.4.2
constraint in the pyproject.toml, since that was the newest version at that point. Now I want to know if a version >=4.x
was published, so I can check if I want to upgrade to it and possibly see the changelog for upgrade instructions.Being able to check this for all constraints at once, e.g. via
poetry show --outdated-constraints
, would be very helpful. This is similar topoetry show --outdated
, but just operates on the entries in thepyproject.toml
and not all sub-dependencies, and does not include updates that might possibly work withpoetry update
(if cross-dependencies do not forbid them).This is a small POC that implements such an overview:
Thanks for considering this! And thanks for your awesome work on poetry!
The text was updated successfully, but these errors were encountered: