-
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
poetry update <single-pkg>
updates a different package with extras specification
#3128
Comments
@immerrr I found your issue after experiencing the same but was able to resolve it with the following:
Without digging, I think this happens because the cc @finswimmer |
@skylerwshaw that's good that at least in some real-life examples it is possible to work this around. However, please note that the repro included in the original message cannot have an old-format lockfile, because it only includes |
Btw, I have just retried the same repro with v1.1.4, because I had hope that the new fixes for extra dependencies would help, but looks like the behaviour is still the same, poetry updates
|
Any update on this? On 1.1.6 not only does |
One thing I'd note, is that on systems that do this, it's possible to get into some pretty tricky situations where it's hard to work out what you can update, I've certainly experienced this with pip-tools/pip-compile and on ruby with rake. |
Relates to #4612. The attached PR seems to resolve this issue, too. |
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. |
-vvv
option).Issue
It looks like packages with extras circumvent the whitelisting restriction when updating a single package with
Here's a repro:
0.10.2
, and dopoetry update
^0.10.2
, but this time dopoetry update decorator
decorator
packagewatchdog is updated to `0.10.3`
What leads me to believe this is somehow related to the extras specification, is that ...
... if I remove the extras and repeat the repro with just `watchdog = {version = "^0.10.2"}`, watchdog is *not* updated to 0.10.3 which is the expected behaviour.
The text was updated successfully, but these errors were encountered: