-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
removes explicit source from lockfile unexpectedly
#8928
Comments
poetry update
removes explicit source unexpectedlypoetry update
removes explicit source from lockfile unexpectedly
Duplicate #8614 please close |
Note that I've tried to apply the fix for #8614 but it doesn't work for this. |
well in that case it is duplicate #8328 instead edit: probably not actually |
#8835 which solved #8614 only handles a fresh lock (without I tried a naive fix in #8948 but that breaks other things (for example if the locked package references a source that does not exist anymore or if an explicit source has been changed in the pyproject.toml). I suppose we have to figure out if a locked package comes from a dependency with an explicit source. However, that's a tough nut to crack for multiple-constraints dependencies with several locked packages with different sources. |
I think I have found a robust solution now. Feel free to try #8948. (It's just missing one more test.) |
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) and have included the output below.Issue
I'm using a in-project virtualenv for this repro, after the initial lock and install, git commit the changes so the worktree is in clean state:
now poetry.lock is modified expectedly after executing
poetry update ruff
:as you can see the jax-releases explicit source has been removed expectedly. It will be fixed if I run
poetry update jaxlib
:this is pretty annoying, and can lead to #3114.
The text was updated successfully, but these errors were encountered: