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, schlamar, steve.dower, tim.golden, zach.ware
Date 2019-02-01.13:17:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The __PYVENV_LAUNCHER__ variable gets set by each launcher instance. We get one launcher process for every level of nesting, and the last launcher to run sets the final value that will be seen by the real python.exe. Possibly the launcher could resolve the home values until it reaches a solid python.exe (i.e. no pyvenv.cfg file), and thus avoid the nested chain of launcher processes and ensure that the real python.exe sees the correct value of __PYVENV_LAUNCHER__.
Date User Action Args
2019-02-01 13:17:25eryksunsetrecipients: + eryksun, paul.moore, tim.golden, schlamar, zach.ware, steve.dower
2019-02-01 13:17:23eryksunsetmessageid: <>
2019-02-01 13:17:23eryksunlinkissue35872 messages
2019-02-01 13:17:23eryksuncreate