[issue31363] __PYVENV_LAUNCHER__ breaks calling another venv's interpreter

Ned Deily added the comment: This issue has been fixed in the code for Issue22490 which will be released in Python 3.8.3 and 3.7.8. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installs f

[issue31363] __PYVENV_LAUNCHER__ breaks calling another venv's interpreter

Changes by Ned Deily : -- nosy: +ned.deily, vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue31363] __PYVENV_LAUNCHER__ breaks calling another venv's interpreter

New submission from Ilya Kulakov: There are 2 venvs. One has the pkg_resources (pkgr_venv) package installed, another (venv) doesn't. Venv without pkg_resources is currently active. Works: $ /python -c "import pkg_resources" Doesn't work: $ python -c "import subprocess; subprocess.check_call