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 mathstuf, paul.moore, steve.dower, tim.golden, zach.ware
Date 2020-11-02.17:48:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1604339302.92.0.913019040229.issue42228@roundup.psfhosted.org>
In-reply-to
Content
If `<directory of python.exe>\Lib\os.py` exists, then you shouldn't need either a registry entry or environment variable.

This sounds the same as the approach used on GitHub Actions and Azure Pipelines, and also through the packages at https://www.nuget.org/packages/python. These work fine, as far as I'm aware.

If there is some other reason you need PYTHONHOME to be set inside an activated virtual environment, you could set it _after_ activating the environment, or just modify the Activate.ps1 that is included in your tarball.

However, I seem to recall there were some fairly obscure bugs if a venv didn't resolve itself normally. So your best bet is to make sure that it can be resolved without needing the setting.
History
Date User Action Args
2020-11-02 17:48:23steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, mathstuf
2020-11-02 17:48:22steve.dowersetmessageid: <1604339302.92.0.913019040229.issue42228@roundup.psfhosted.org>
2020-11-02 17:48:22steve.dowerlinkissue42228 messages
2020-11-02 17:48:22steve.dowercreate