This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients paul.moore, pierreglaser, pitrou, steve.dower, tim.golden, zach.ware
Date 2019-09-10.16:13:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1568132006.72.0.556997895631.issue38092@roundup.psfhosted.org>
In-reply-to
Content
The difference is that launching sys._base_executable *without* __PYVENV_LAUNCHER__ set (because env is not being passed) should lose you access to anything installed into the venv. You may also need to import something from the venv in order to see the issue.

Launching sys.executable will hit the launcher that sets the environment variable. Setting the environment correctly and launching sys._base_executable will also load correctly. The latter is theoretically required for correct handle sharing, but that may depend on which Windows version you're running.

I'd like to see both changes in the PR. Just setting the environment variable doesn't really improve the situation at all.
History
Date User Action Args
2019-09-10 16:13:26steve.dowersetrecipients: + steve.dower, paul.moore, pitrou, tim.golden, zach.ware, pierreglaser
2019-09-10 16:13:26steve.dowersetmessageid: <1568132006.72.0.556997895631.issue38092@roundup.psfhosted.org>
2019-09-10 16:13:26steve.dowerlinkissue38092 messages
2019-09-10 16:13:26steve.dowercreate