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 eryksun
Recipients eryksun, paul.moore, steve.dower, tim.golden, vinay.sajip, zach.ware
Date 2019-01-24.18:44:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1548355472.53.0.626317311978.issue35811@roundup.psfhosted.org>
In-reply-to
Content
> 1. Is there a possibility that 3rd party applications like pip 
> could see bugs with Python 3.7.2?

A bug occurs when running an entry-point script, such as pip.exe, for a system- or user-installed Python 3.7.2+ from the context of a virtual environment for 3.7.2+. The script executable redirects to run `"path\to\python.exe" "path\to\<script_name>.exe"`. This will inherit __PYVENV_LAUNCHER__ and thus run in the virtual environment. The environment doesn't have to be activated. People use inactive virtual environments for various purposes, so it doesn't defy my expectations that someone may have a problem. I think the distlib launchers should make the same change to unset __PYVENV_LAUNCHER__, which is why I nosied Vinay.
History
Date User Action Args
2019-01-24 18:44:33eryksunsetrecipients: + eryksun, paul.moore, vinay.sajip, tim.golden, zach.ware, steve.dower
2019-01-24 18:44:32eryksunsetmessageid: <1548355472.53.0.626317311978.issue35811@roundup.psfhosted.org>
2019-01-24 18:44:32eryksunlinkissue35811 messages
2019-01-24 18:44:32eryksuncreate