-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
Controlling venv from venv no longer works in 3.7.2 #80054
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
Comments
Controlling a venv from the python.exe from another venv does not work since 3.7.2 on Windows. This is probably related to the change
This is obviously related to bpo-35872, but this could be a different bug. When a Python script in a venv wants to control another venv by running commands like This can be reproduced with pipx (https://github.com/pipxproject/pipx-app) by running
This results in pip installing to venvs\pipx-app and not in venvs\tox. I assume a simpler reproduction might be (but I cannot check this anymore as I'm back on 3.7.1 right now):
Downstream bugreport in pipx is pypa/pipx#81. |
So with the fix for multiprocessing, we currently rely on __PYVENV_LAUNCHER__ remaining set throughout the process. However, it may be better to add a "sys.base_executable" property instead and clear the __PYVENV_LAUNCHER__ variable once we've read it. Then we can set it again in multiprocessing and launch the base executable, and otherwise default to launching the redirector. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: