Tim Smith added the comment: I spoke prematurely; I recently rediscovered that the persistence of __PYVENV_LAUNCHER__ poisons the sys.executable of virtualenv interpreters launched as a subprocess of another Python interpreter:
$ virtualenv -p python3 test $ test/bin/python3 -c 'import sys; print(sys.executable)' /Users/tim/test/bin/python3 $ /usr/local/bin/python3 -c 'import subprocess; subprocess.call(["/Users/tim/test/bin/python3", "-c", "import sys; print(sys.executable)"])' /usr/local/bin/python3 $ /usr/local/bin/python3 -c 'import subprocess, os; del os.environ["__PYVENV_LAUNCHER__"]; subprocess.call(["/Users/tim/test/bin/python3", "-c", "import sys; print(sys.executable)"])' /Users/tim/test/bin/python3 If __PYVENV_LAUNCHER__ can be unset before script execution begins, that seems ideal. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22490> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
