-
-
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
Version resolution sometimes fails when no previous virtual env exists #2435
Comments
Huh, I've been wondering about that bug. I am not sure what exactly is the cause but the fact that it only happens in fresh environments is new information for me. does this happen with master also? |
Yep, happening with the latest master. Let me see if I can get the commit that introduced it for you... |
Yeah that makes perfect sense, try against master now that I updated |
Fixed on master. 🎉 |
Argh, @techalchemy, you're going to hate me but I jumped the gun on this. It's still happening, although possibly less often - I now can't always reproduce it just by removing the virtualenv. Here's my terminal output from running Output (search for "TypeError")
Some observations:
I'm at a bit of a loss on where to dig next. |
- Prevents re-preparation of deleted `PKG-INFO` files - Fixes #2435 Signed-off-by: Dan Ryan <dan@danryan.co>
Weird one, but I can reproduce the below consistently. I think it's due to resolution relying on the existing state of the virtualenv, but I could be missing something.
Note: This bug is new in
2018.6.25
- I don't get it in2018.5.18
.$ python -m pipenv.help output
Pipenv version:
'2018.6.26.dev0'
Pipenv location:
'/Users/greysteil/code/pipenv/pipenv'
Python location:
'/usr/local/opt/python/bin/python3.6'
Other Python installations in
PATH
:2.6
:/usr/bin/python2.6
2.6
:/usr/bin/python2.6
2.7
:/usr/bin/python2.7
2.7
:/usr/bin/python2.7
3.6
:/usr/local/bin/python3.6m
3.6
:/usr/local/bin/python3.6
3.6
:/usr/local/bin/python3.6
3.6.5
:/usr/local/bin/python
3.6.5
:/usr/local/bin/python
2.7.10
:/usr/bin/python
3.6.5
:/usr/local/bin/python3
3.6.5
:/usr/local/bin/python3
PEP 508 Information:
System environment variables:
TERM_PROGRAM
PYENV_ROOT
TERM
SHELL
CLICOLOR
TMPDIR
Apple_PubSub_Socket_Render
TERM_PROGRAM_VERSION
OLDPWD
TERM_SESSION_ID
USER
SSH_AUTH_SOCK
__CF_USER_TEXT_ENCODING
LSCOLORS
PATH
PWD
EDITOR
LANG
XPC_FLAGS
RBENV_SHELL
XPC_SERVICE_NAME
HOME
SHLVL
LOGNAME
_
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:/usr/local/opt/erlang@20/bin:/Users/greysteil/.pyenv/bin:/Users/greysteil/.cargo/bin:/usr/local/heroku/bin:/Users/greysteil/.rbenv/shims:/usr/local/bin:./node_modules/.bin:.bundle/binstubs:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Library/TeX/texbin:/usr/local/sbin
SHELL
:/bin/bash
EDITOR
:subl -w
LANG
:en_GB.UTF-8
PWD
:/Users/greysteil/code/python-test
Contents of
Pipfile
('/Users/greysteil/code/python-test/Pipfile'):Expected result
Running
pyenv exec pipenv lock -v
should work fineActual result
Running
pyenv exec pipenv lock -v
produces:Error details
I only get the above error when I run the command for the first time in a fresh virtual env. Running a second time I get successful resolution.
Steps to replicate
Note, I have Python 3.6.5 (default) and Python 2.7.15 installed via pyenv.
The text was updated successfully, but these errors were encountered: