Skip to content
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 --venv returns incorrect virtual env path #2896

Closed
pdpark opened this issue Sep 28, 2018 · 2 comments
Closed

pipenv --venv returns incorrect virtual env path #2896

pdpark opened this issue Sep 28, 2018 · 2 comments
Labels
reported bug Status: Needs More Information This issue does not provide enough information to take further action.

Comments

@pdpark
Copy link

pdpark commented Sep 28, 2018

Issue description

pipenv --venv

Returns a path that is a concatenation of my actual virtual env with the location of the pyenv python version used when creating the env.

Expected result

Just the path to the virtual env:

/Users//.venvs/

Actual result

/Users//.venvs//Users//.pyenv/shims/python

Steps to replicate

Environment created from existing requirements.txt using pipenv install --ignore-lock

From my .zshrc file:

pyenv

export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
if command -v pyenv 1>/dev/null 2>&1; then
eval "$(pyenv init -)"
fi

pipenv

export WORKON_HOME=~/.venvs
export PIPENV_PYTHON=$PYENV_ROOT/shims/python
eval "$(pipenv --completion)"

@techalchemy
Copy link
Member

Hi, I'm going to go ahead and guess that you are using pyenv-virtualenv because I happen to know that it puts virtualenvs in your pyenv root directory.

You've described a few steps, but I really need you to paste the output of all of the commands required to replicate whatever you're seeing, including the output. Simply describing this kind of problem isn't usually enough for us to really understand the issue, so if possible step by step instructions on exactly what to type in, with copy-pasted text of exactly what you saw as output, would be infinitely helpful in debugging this.

@techalchemy techalchemy added reported bug Status: Needs More Information This issue does not provide enough information to take further action. labels Oct 20, 2018
@techalchemy
Copy link
Member

Hey there, we haven't heard back and we haven't heard any other reports of this, so I'm going to go ahead and close this for now. Thanks for the report, and feel free to let us know if this comes up again in the new release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reported bug Status: Needs More Information This issue does not provide enough information to take further action.
Projects
None yet
Development

No branches or pull requests

2 participants