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

inconsistent pipenv behaviour with symlinked directory and PIPENV_PIPFILE #4115

Open
pbadenski opened this issue Jan 28, 2020 · 0 comments
Open
Labels
Contributor Candidate The issue has been identified/triaged and contributions are welcomed/encouraged. hacktoberfest triage Type: Possible Bug This issue describes a possible bug in pipenv.

Comments

@pbadenski
Copy link

Issue description

When pipenv is run with PIPENV_PIPFILE and pointing to a directory that is a symlink, .venv location is not resolved correctly.

Expected result

Running:

cd DIR
pipenv --venv

and

PIPENV_PIPFILE=DIR/Pipfile pipenv --venv

and

PIPENV_PIPFILE=$(readlink -f /root/kaa/Pipfile) pipenv --venv

should all give the same output if DIR is a symlink.

Actual result

# ls -la kaa
lrwxrwxrwx 1 root root 27 Jan 28 06:23 kaa -> /root/kaa-2020-01-28-062244

# PIPENV_PIPFILE=/root/kaa/Pipfile pipenv --venv
/root/.local/share/virtualenvs/kaa-E5w9dr-j

# PIPENV_PIPFILE=$(readlink -f /root/kaa/Pipfile) pipenv --venv
/root/.local/share/virtualenvs/kaa-2020-01-28-062244-UsgZQKBN

# cd kaa
~/kaa# pipenv --venv
/root/.local/share/virtualenvs/kaa-2020-01-28-062244-UsgZQKBN
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Contributor Candidate The issue has been identified/triaged and contributions are welcomed/encouraged. hacktoberfest triage Type: Possible Bug This issue describes a possible bug in pipenv.
Projects
None yet
Development

No branches or pull requests

2 participants