-
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
All dependencies are always updated #1612
Comments
Hello @wylee , thanks for reporting. Could you please try to describe a step-by-step instruction to reproduce the issue? I wasn't able to do this until now. fin swimmer |
I started with Poetry 0.12.17 then upgraded to 1.0b3. This issue wasn't present on either of those versions. Then I upgraded to 1.0b4 and this started happening. I figured it was a temporary issue, so I waited for a couple more beta releases (b5 and b6) to come out. I'm now on 1.0b6, and I'm still seeing this behavior. This is the output for the
And every time I run
|
I just tried deleting my project's virtualenv and then re-running |
So, I was able to reproduce this in the following way:
One thing I noticed here is that starting with 1.0b4 virtualenvs are created in ~/Library/Caches/pypoetry/virtualenvs even though my poetry config looks like this:
Edit: It appears the config format changed slightly in 1.0b3, but that doesn't seem to be relevant to this issue. |
I stumbled across another way this can happen with 1.0b4, 1.0b5, and 1.0b6:
|
Thanks the detailed steps to reproduce. Unfortunately I am still unable to reproduce. What's the output of |
I installed poetry using pipx. Output of
Based on that, I think I figured out what's happening. When So, that's my mistake (and sorry for the noise), but I do think it might be good if poetry showed at least a warning, or even aborted, in the case of an invalid virtualenv. |
I am also getting this in versions 1.0.0b4-1.0.0b7; in my case, at least, it appears to be related to pip installing dependencies in a location poetry isn't expecting (e.g., if they are pip installed with the When this is the case, it seems like poetry is running some pip-related command in the background (maybe?), but it doesn't result in any changes, which is why it always installs them all. I'll see if I can make an easily reproduced docker image. |
I experience this issue when using an in-project virtualenv (.venv/). Similarly to the others, I did not experience the issue on earlier beta versions. The problem is present on Poetry version 1.0.0b8.
|
@pappasam What's the output of |
@sdispater hmm, strange, but I've re-run in the same project and no longer have the problem. Not sure how to replicate, I apologize:
|
I too am seeing this problem having upgraded from version 0.12.17 to 1.0.0b8.
Doing a |
I faced this issue again on 1.0.3 windows. Could you please reopen this issue? Thanks! |
I have the same issue on 1.0.3 on mac |
and BTW. it's fine on linux (I use archlinux personally) |
This should be a pretty basic feature of a dependency manager: NOT wastefully (both in time and in network usage) always updating every package. I'm on Mac and have the same problem. I tried reverting to 1.0.0 too and while it's better, it still seems to always update a couple of packages. Please add a test after fixing this issue. Until then, I'm switching back to pipenv. |
This issue is blocking as poetry updating everything to the same version. The most interesting and annoying effect of this is that it uninstalls dependencies that poetry depends on!
and this leads to the above exception: |
I just tried adding
Poetry is installed via Homebrew on Mac.
|
Yeah... This is the reason why I switched from pipenv to poetry. Now it behaves exactly the same... @sdispater Why do you think that I want to always update dependencies? Actually, I use dependency manager in order to control updates. And by control I mean that I will update only when I decided to, not when dependency manager wants... |
@sdispater Please, reopen this issue. |
I have the same issue on Fedora 31 and using |
Same but inside docker container. Running it without creating virtualenv. |
My team noticed that some of us were having this issue and others weren't, and we found that people who installed poetry with homebrew were the ones who had the issue. That might be relevant to tracking down what's causing this. |
OMG, this is CLOSED issue, please, reopen it. |
@willmcmain I've been installing poetry using pipx, and that's been working fine (never tried installing it via Homebrew). I wonder if the Homebrew package configures things a certain way that could cause this. Here's the current formula (don't have time to inspect it right now): https://github.com/Homebrew/homebrew-core/blob/master/Formula/poetry.rb |
@grski I don't think it's a homebrew thing per se, just that the homebrew formula, especially how it sets up sys.path, might give some clue as to what the issue is. |
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. |
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option). [N/A]OS version and name: macOS Catalina (10.15.1)
Poetry version: 1.0b4, 1.0b5, 1.0b6
Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/wylee/53e74a3413df25e1b594803e193d40d4
Issue
Since 1.0b4, when running
poetry update
, all of my dependencies are always updated. I've tried clearing the cache and deletingpoetry.lock
.#1582 is similar but seems to affect only project that use a private package index.
The text was updated successfully, but these errors were encountered: