Poetry update does nothing yet manually adding (with wildcard) causes changes #9844
Comments
worthy7
added
kind/bug
|
When you Different inputs may lead to different outputs. Different commands behave differently. I see no reason to believe that this is a bug. |
|
That's a very birds-eye way of looking at it, but if you look at the details, it doesn't make sense. When you have a sub-dependency already installed, and you |
apparently, yes! Often there is more than one valid solution to a set of requirements, and the one that poetry finds depends on the exact path that the search takes. By giving it different inputs I expect you are nudging it onto a different path. If you care about the versions of packages that you get, then use tighter constraints than |
|
Ok in this instance, how is it different? I thought that if I specify * as the version, then any version is allowed. So what's wrong with the currently installed one that it felt it needed to change it? |
|
I did not say there was something "wrong" with the currently installed one, I said that the exact solution that poetry finds may vary according to the exact path that the search takes. eg maybe the first solution happened to find an older version of package Again: if you care about the versions that are installed: you should express that in your dependencies. |
|
Ok I think that sounds a bit weird, but probably I need to look at the docs more if that's the case. What about the other problem, that it is failing to install tensorflow - shouldn't it have resolved all/what packages it needed before going ahead with an install? |
|
resolution is cross-platform, if projects have not published distributions for specific platforms then that is only discovered at install time |
|
OK thanks. Does wildcard stop any updates from happening when running poetry update? |
|
No |
|
Not sure whether this is related, but in case it is: |
|
Not related (and also not correct) |
|
No I totally don't do that, thanks for that tip!!
…On Tue, 19 Nov 2024, 18:53 Hugo Buddelmeijer, ***@***.***> wrote:
Not sure whether this is related, but in case it is: poetry update
requires --with to update packages in a dependency group. Since
everything is in your dev group, running just poetry update will do
nothing, you need to do poetry update --with=dev. Maybe you already do
that, it's not clear (to me) what update command you used.
—
Reply to this email directly, view it on GitHub
<#9844 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEKWH3NWR7LZI766LYLVKT2BMDBNAVCNFSM6AAAAABRYBT65WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBVGIYTCNZRGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Probably indeed not related because the dependency group is not optional. |
Description
With poetry show, I can see a package is installed
nvidia-nvjitlink-cu12I know it is a dependency of another package.
To check everything is up to date, I run
poetry updateand nothing happens.Yet, when I manually add the package (with wildcard) it tries to install another version. This makes no sense.
Workarounds
None
Poetry Installation Method
system package manager (eg: dnf, apt etc.)
Operating System
Debian 12
Poetry Version
1.8.4
Poetry Configuration
Python Sysconfig
Example pyproject.toml
Poetry Runtime Logs
The text was updated successfully, but these errors were encountered: