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

WORKAROUND: Force usage of pythonX.X for -m venv #245

Open
wants to merge 2 commits into
base: master
from

Conversation

Projects
None yet
3 participants
@seliger

seliger commented Dec 28, 2017

Uses ${PYENV_VERSION:0:3} to force venv to correctly
make all of the necessary symlinks in the virtualenv's
bin directory.

Refer to issue #206 for details.

seliger added some commits Dec 28, 2017

WORKAROUND: Force usage of pythonX.X for -m venv
Uses ${PYENV_VERSION:0:3} to force venv to correctly
make all of the necessary symlinks in the virtualenv's
bin directory.
WORKAROUND: Force pythonX.X for -m venv (take 2)
While the first commit seemingly produced the intended
results, the changes inadvertantly and unexpected broke
all of the unit tests. This commit represnts changes to
both pyenv-virtualenv and its associated tests to employ
the force pythonX.X workaround.
@DuncanHills

This comment has been minimized.

Show comment
Hide comment
@DuncanHills

DuncanHills Feb 14, 2018

Can the authors consider this pull request? In addition to the aforementioned use cases (tox), this bug affects using Pants and PEX with pyenv-virtulalenv.

DuncanHills commented Feb 14, 2018

Can the authors consider this pull request? In addition to the aforementioned use cases (tox), this bug affects using Pants and PEX with pyenv-virtulalenv.

@robertlagrant

This comment has been minimized.

Show comment
Hide comment
@robertlagrant

robertlagrant Oct 8, 2018

+1

This is a genuine issue for tox users.

robertlagrant commented Oct 8, 2018

+1

This is a genuine issue for tox users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment