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

FIX for virtualenv is not compatible with this system or executable #1208

Closed
wants to merge 1 commit into
base: master
from

Conversation

2 participants
@vesellov

vesellov commented Oct 4, 2018

When using tox on MacOS it makes impossible to create a new "custom" venv. This tiny fix should solve that issue. Here is what I am getting from tox:

actionid: py36
msg: getenv
cmdargs: '/home/veselin/repo/venv/bin/python3.6 -m virtualenv --python /home/veselin/repo/venv/bin/python3.6 py36'

Already using interpreter /home/veselin/repo/venv/bin/python3.6
Using base prefix '/usr/local/bin/../Cellar/python/3.6.5/bin/../Frameworks/Python.framework/Versions/3.6'
New python executable in /home/veselin/repo/.tox/py36/bin/python3.6
Also creating executable in /home/veselin/repo/.tox/py36/bin/python
ERROR: The executable /home/veselin/repo/.tox/py36/bin/python3.6 is not functioning
ERROR: It thinks sys.prefix is '/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6' (should be '/home/veselin/repo/.tox/py36')
ERROR: virtualenv is not compatible with this system or executable

I saw many other similar reports in the web and decided to create that Pull Request to fix it.

@gaborbernat gaborbernat force-pushed the pypa:master branch 5 times, most recently from 9b9e4aa to 9d8d241 Oct 22, 2018

@gaborbernat

This comment has been minimized.

Contributor

gaborbernat commented Oct 26, 2018

superseded by #1227

gaborbernat added a commit that referenced this pull request Oct 26, 2018

ensure prefix path is absolute (#1227)
Replaces #1208 as the PR is not edit-able.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment