-
-
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
2018.11.26: pipenv emits pythons errors when creating a virtualenv #3363
Comments
It seems |
Hmm. Should it ever have been? I've never used pythonz directly. I thought it was just a pipenv dependency that it managed when I installed pipenv. For kicks, I just uninstalled and re-installed pipenv 2018.11.26 and am still having the issue. |
Can you provide the output from |
Oh nvm just saw your message. I just want to confirm there is no rogue version of pipenv on your path somewhere. Can you check |
Thanks! |
Ah ok. And yeah the bug makes sense. I’ll just tag it upstream and make sure it gets fixed |
Any word on when a fix will be released for this? I am having this problem its preventing me from installing the pipenv requirements. I have tried @commandtab 's workaround with no such luck. |
I can not get pipenv to work at all with the current version.
I tried installing with python3.7 from homebrew, and same issue. It seems like there's no urgency here, or that it's not a big problem. Am I missing something, or is pipenv completely broken with the current version? |
The current release sure seems hosed to me. Another temporary workaround I saw in a past issue was to specifically pass in a
I've been doing this with success for the time being 😬 |
That workaround wasn't working for me. I had to downgrade to
As far as I can tell, pipenv has been completely broken since October. |
@techalchemy Any word on an upstream tag fix? pipenv virtualenv creation still requires workarounds for invocation. Thank you ❤️ |
This was a bit rough with all the other fixes that needed to be integrated but I think CI will pass now and this will be fixed with #3330 -- sorry for the trouble |
Still issue persists, any idea when this fix will be released. |
Same issue here. Can confirm @command-tab's workaround still works. |
This definitely still happens with homebrew pipenv and python… kind of surprised there isn't a test to cover it seeing how long this issue has been around… |
I can also confirm that this problem is still happening, despite this GitHub issue being closed. Do the maintainers need a new issue to be created? |
Same issue with Ubuntu 18 LTS installed in Windows Subsystem for Linux. Workaround works for me. |
@techalchemy this issue still seems to exist. Can you please either reopen it or make it clear that you want a new issue to be created? Thanks. |
same here |
@techalchemy please take a look again |
Same issue here on macOs Mojave and python 3.7 |
Me too:
Everything works fine once I comment out this line in my Pipfile:
|
ahhhh this worked for me, thank you! |
@JarredStanford @edsu @command-tab After getting both workarounds and I was able to get it to work, I removed them and tried a third time to ensure the environment was still causing an issue (narrator: it was). @techalchemy Would you think it best I open a new issue, would you like me to run additional diagnostics, or something else? |
I m using wsl2 with arclinux (manjaro) works for me. |
Can confirm this happens under WSL with Ubuntu 18.04 LTS. It seems like pipenv is going in search of a python interpreter rather than using the one that it is being executed under, and in-so-doing is traversing PATH in backwards order. I have multiple python environments installed, and whenever I manually remove one from PATH, pipenv will find a different one and complain about that one instead. |
I'm seeing the same issue under WSL with Ubuntu 18.04 LTS. |
Also I am affected, using WSL 1 and Ubuntu 18.04. Workaround |
The reason for the last part of the exception, i.e. this bit:
... is because there is a bug in the call to print an error when handling the first exception. This bug appears to have already been fixed in master back in Jan 2019 - 574fe73#diff-a59595db75020aeb9f688d6a0b4818e6L162. But since the latest version of pipenv is 2018.11.26, I imagine most don't have a fixed version. One can patch it manually. Open sys.stderr.write("Error %s while executing command %s", exc, " ".join(cmd._parts)) ... to this: sys.stderr.write(f"Error {exc} while executing command " + " ".join(cmd._parts)) You will now get a more accurate exception report. In my case, the issue is to do with WSL Linux-based pipenv detecting Windows-based Python installations and having trouble running them, which is kind of obvious:
For WSL users, I believe the issue can be alleviated by ensuring that any requirements on your Python version in
Hope this helps. |
Not sure how much this helps, but deleting the Pipfile, running |
I keep finding this page when trying to run failure tests, so updating the README that way: pypa/pipenv#3363 (comment)
* Update failure tests README I keep finding this page when trying to run failure tests, so updating the README that way: pypa/pipenv#3363 (comment) Co-authored-by: Hanefi Onaldi <Hanefi.Onaldi@microsoft.com> Co-authored-by: Hanefi Onaldi <Hanefi.Onaldi@microsoft.com>
* Update failure tests README I keep finding this page when trying to run failure tests, so updating the README that way: pypa/pipenv#3363 (comment) Co-authored-by: Hanefi Onaldi <Hanefi.Onaldi@microsoft.com> Co-authored-by: Hanefi Onaldi <Hanefi.Onaldi@microsoft.com>
Issue description
Possibly related to #3229, pipenv continues to throw errors when creating a virtualenv:
Expected result
Expected no error logging while simply creating a virtualenv.
Actual result
virtualenv creation fails.
Steps to replicate
pipenv --support
also emits these errors and fails to collect support information!The text was updated successfully, but these errors were encountered: