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 pyscripter
Recipients Dieter Weber, paul.moore, pyscripter, steve.dower, tds333, tim.golden, vstinner, zach.ware
Date 2019-02-04.17:01:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
"Personally, I am 100% against letting an embedded runtime automatically pick up any settings from the environment. You don't know where they came from."

Why is that?  When the embedding application is using Py_SetPythonHome there is clear intent to use a specific python setup.  This is no different to using any other Python setup.  Why venvs should be treated differently that standard installations?

As to manually setting the path, why pass the burden to the embedding application.  The idea is that python, in the embedding application, should work as in the python executable.   Trying to match the complex and evolving algorithms that python uses to setup the path, is a huge and unnecessary burden on the embedding application.
Date User Action Args
2019-02-04 17:01:28pyscriptersetrecipients: + pyscripter, paul.moore, tds333, vstinner, tim.golden, zach.ware, steve.dower, Dieter Weber
2019-02-04 17:01:26pyscriptersetmessageid: <>
2019-02-04 17:01:26pyscripterlinkissue35706 messages
2019-02-04 17:01:26pyscriptercreate