You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3.7 has been obsolete for a while, with 3.8 onwards we can use https://peps.python.org/pep-0587/ to set the startup configuration, allowing (finally) for proper configuration of venvs.
From 3.14, we could even use the PyInitConfig mechanism from PEP741, which gives us full control over the initialization. For now, we'll just hardcode the offsets, similar to how we store the offsets in the PyHEAPTYPE struct :/
I think we might skip this and go directly for the Python 3.14 mechanism which does not require us to keep offsets into structs (yay!). For versions before 3.15, setting ProgramName should do the trick and we might be able to simplify things. My idea is to derive it (and also the runtime DLL) automatically from "normal" venvs that set VIRTUAL_ENV.
Activity
filmor commentedon Oct 24, 2025
I think we might skip this and go directly for the Python 3.14 mechanism which does not require us to keep offsets into structs (yay!). For versions before 3.15, setting
ProgramNameshould do the trick and we might be able to simplify things. My idea is to derive it (and also the runtime DLL) automatically from "normal" venvs that setVIRTUAL_ENV.filmor commentedon Dec 6, 2025
PyPreConfigis separate from this, should be implemented as well.