Steve Dower added the comment:
> I've worked around it so far by just ignoring `Activate.ps1` completely and
> setting up PATH, PYTHONHOME, and PYTHONPATH instead
This sounds like the right approach. Though if you're genuinely embedding
Python in your application you should consider just
Ben Boeckel added the comment:
We build our own applications which run Python interpreters internally, so the
auto-discovery won't work. It also doesn't seem to work for venvs either since
the venv's `python.exe` is under `Scripts` which makes it not able to find
things either on its own.
Steve Dower added the comment:
If `\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
New submission from Ben Boeckel :
On Windows, we are extracting a tarball of a Python installation for CI (to
avoid needing to juggle umpteen Python installs on umpteen machines). This
requires `PYTHONHOME` to be set to use properly since there is no registry
entry for the "installation".
