Stephen Moore <delfick...@gmail.com> added the comment: It appears the problem doesn't appear when using python3 -m venv.
Also it seems __PYVENV_LAUNCHER__ is set to the virtualenv's python except when it's a python3.6 virtualenv and we os.execv from python3.6, where it's set the system python. Should I be making an issue with the virtualenv project? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31660> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
