-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
pipenv fails to install all my packages, and then installs all of them #1356
Comments
I'm also struggling with this issue, are there any updates or solutions? |
Hi @JacekJab sorry you are running into this -- the initial failure isn't actually a bug, per se, I'm guessing it is related to concurrent installs from a non-pypi repository. They initially failed and then fell back to sequential installation. As far as the click installation, you will need to provide the full context of the command you ran, your |
closing since they are successful in the end — we'll need much more information in order to replicate |
I have the same issue with latest version of pipenv. I'm curious, @JacekJab are you using Nexus for your repositories? |
I'm having the same issue. Pretty annoying and should be looked into. |
@pawelswiecki please provide details including the output and Pipfile you used per the issue template. Telling us to look into something with no additional detail is not productive and as volunteers would rank pretty high on the list of things we also find annoying |
I'm having the same issue. I'm running My
My
The output (truncated because the rest of it is just test output, which is okay):
|
does this work if you upgrade pip first in your CI build with |
Nope, same problem. Here are the steps I took and the output: Okay I removed
Now I deleted
Running
|
FYI: Just running I'm not a Python dev so I can't help too much in providing useful info so I apologise ahead of time. |
@wjlow I think what @techalchemy meant is you need to upgrade the pip inside the tox-managed environment, not the one used by your project, i.e. add it to the commands =
pipenv run python -m pip install --upgrade pip
pipenv install --skip-lock
pipenv install --dev --skip-lock
pipenv run flake8 --version
pipenv run flake8 dag
pipenv run pytest |
Same issue, unfortunately! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Can someone confirm if this is still an issue? |
I'm having the same issue on my CI machines (gitlab runner). I believe it's happening due to some race condition but I can't really nail it down. |
I'm also having it. |
Please provide output as it’s not possible to debug otherwise. |
|
We're seeing the same thing in our jenkins builds. This output is typical:
We're using the EDIT: Actually, we were using |
PLEASE PROVIDE CONTEXT BEFORE PASTING OUTPUT INTO AN OPEN ISSUE. We know what the symptom looks like. It only helps us if you provide the context that can help reproduce it. Think of it like having a dog that is sick. The issue roughly says ‘my dog is vomiting, it happens when we go on walks!’ And a bunch of others now yelling ‘my dog is also vomiting!’, ‘my cat threw up once!’, ‘my turtle threw up yesterday!’. Did they each eat bad food? What food? Were they eating the same food? If I get a turtle myself, can I copy you and get mine to vomit? Was there some other factor in play? Hopefully this analogy makes sense. Please include details about the error and not just a dump showing that the error has occurred. |
So PLEASE tell me, what context you would like to get. Because a doctor doesn't simply stand there, waiting for the patient to tell everything without asking questions. |
Apologies, but it is essentially impossible for me to ask you for all of the possible variables that make your environment different from our CI and the vast majority of people who use pipenv. Are you all using exclusively private repositories? Have you tried changing anything? With any success? Between which versions of pipenv did this begin occurring? I know it seems like I should have some answers but I am completely blind to the things that make your environments unique. |
And unless someone can spend the time diagnosing that I probably need a way to reproduce this -- a dockerfile or something |
We also have private repo and same issue.
I'll try to isolate the issue with a dockerfile for you, good idea!
Le dim. 7 oct. 2018 à 09:33, Dan Ryan <[email protected]> a écrit :
… And unless someone can spend the time diagnosing that I probably need a
way to reproduce this -- a dockerfile or something
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1356 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAcK2QorIRkvNx8xFFvDyC3RMCOiTMjIks5uibxugaJpZM4Rs3S3>
.
|
I have to same issue. and Pipenv detected some packages installed in the environment at the beginning, but the installation timeout. and then Pipenv started to reinstall all the packages again. |
@techalchemy I have a Dockerfile which reproduces this problem, or perhaps a worse one. https://gist.github.com/hjwp/72489330407b85d7c52d29ec77c587e0 In our case pipenv reports some failures on first install, then reports attempts to reinstall, and then actually fails to install some packages altogether (but does not report an explicit error about this) you can verify this with
|
I wanted to bump on this to see if there's been any resolution |
|
everyone, i don't work on the pipenv project, but let me say on behalf of the maintainers: yes, it's useful to know when a bug affects more people. it's not useful to receive nagging comments saying "has this been fixed yet?". if it's really bothering you, the right thing to do is fix it yourself. @nickwilliams-eventbrite, if you are bumping into this problem literally thousands of times like you say, it sounds like it would be a good investment on your part put some time into fixing it yourself, and saving your team time and frustration. sorry for getting a bit preachy! but open source lives and dies on goodwill, and it's eroded a tiny bit at a time everyone complains with a "why hasn't this been fixed yet?" at a team of unpaid volunteers.... and if this comment rubs you up the wrong way, remember to blame me, and not the lovely pipenv team ;-) |
Like others, I had this exact same issue. My root cause may not be the same as others, but thought I'd throw it in here to help those in a similar situation. I'm using an old early 2011 MacBook Pro running macOS High Sierra (10.13.6). TL;DR - My build environment was out of whack. For me, the fix was reinstalling Xcode Command Line Tools with My debugging steps:
In particular, this line stuck out:
For me, this issue would've only been triggered by packages which have to be compiled. This may or may not be similar to what others are experiencing. If so, maybe more verbose warning / error messaging from pipenv could alert the user to the root cause. Hope this helps others. |
Same issue here (I believe). Offering some additional context/information. (initially confounded with moto getmoto/moto#2465). Ultimately I could reasonably consistently reproduce with something like: Pipfile[[source]] [packages] [dev-packages] [requires] And the docker run command:
|
While installing the below lxml I am getting this error. ERROR: Exception: During handling of the above exception, another exception occurred: Traceback (most recent call last): |
if you still got the error please try using this
It will upgrade the pip, and also fix my problem |
|
I had the same issue. |
GH5:cloud-comer i5$ pip install --upgrade setuptools By the way, I thought I am running Python 3 $ python WARNING: Python 2.7 is not recommended. Python 2.7.16 (default, May 8 2021, 11:48:02) |
Same i am getting error installating all of my package |
Closing this issue as it was reported for much older versions of |
I had a similar issue today with installing dependencies from a
When running
Then finally it shows this at the end:
My issue was a little more obvious though, since I had this output (shortened output):
So all I did was run |
I have found that this problem can also present itself if you made changes to your dependencies in your Pipfile but forgot to "lock" those changes to update the Pipfile.lock file accordingly (behaviour tested and observed in 2022.9.24, 2022.10.4, and 2022.10.25). In our specific situation, we had an internal package from an internal repo using PyPi as an upstream whose dependency declaration had been updated to a higher version in the Pipfile, but the lockfile (Pipfile.lock) still specified an older version. When running "pipenv sync" in our CI pipeline, whatever issue having this discrepancy caused prevented it from succeeding. Once we updated the lockfile accordingly and pushed the change, it resolved the issue. Hope it helps. |
This stackoverflow response seems to solve the issue.. it did for me! |
This works for me:
|
Try to implement fix as seen on pypa/pipenv#1356
The same here I tried to delete Pipfile.lock, upgrade pipenv and setuptools but nothing. |
Hey there,
Clearly, there is some mismatch in the version of the dependencies. So, I would recommend deleting the Pipfile and reinstalling the packages again. To be precise, I have Python version (3.10), pip version (22.0.2), and pipenv version 2023.7.23 . |
In my case, removing the extra Python version from my system, resetting the environment path, and reinstalling it fixed the problem. |
In my case, after running |
Hey Since you're seeing warnings about invalid metadata entries for the Click package, it's a good idea to try updating or reinstalling it. You can do this using pip: "pip install --upgrade click" |
Hi, it might be something that I do not understand or so. I have 2 sources specified and none of them is official pypi, but mirrors, so here is my Pipfile:
Describe your environment
$ python -V
Python 3.6.1$ pipenv --version
pipenv, version 9.0.3Expected result
All packages installed immediatly.
Actual result
Steps to replicate
pipenv install --system
Please also note, that pipenv is installing click==6.7 despite specifying 6.2 version.
The text was updated successfully, but these errors were encountered: