-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
sys.executable and sys.path are wrong when running virtualenv python in subprocess on macOS #1581
Comments
Judging from the output of that virtualenv creation you're using the old legacy version of virtualenv (< |
the output is due to framework builds which are particularly fickle, you'll likely need a workaround similar to this |
I was using the version provided by Macports. Upgrading
|
When launching the virtualenv
python
bynary from asubprocess
from the system binary, the environment in which thesubprocess
call is running looks wrong: e.g. it returns the system python binary assys.executable
.If the virtualenv is created using
venv
, things work as expected.On Linux the bug is not present.
Python Details
OS details
10.15.3 (but I could also reproduce on 10.14)
If I do (using the system python):
python -m venv $WORKON_HOME/test-venv
and then:On the other hand, if I create a virtual env using
virtualenv
:And then
The text was updated successfully, but these errors were encountered: