|
I am trying to write a compiled wrapper that runs Python programs via WinPython, passing an environment similar to the environment that is set up by I have tried comparing the environments generated by my wrapper and by What am I missing? Things I have double checked:
Why it matters for me: I don't actually need to configure anything through |
Replies: 7 comments 2 replies
|
I finally figured out that |
|
Indeed, this is this beautiful line: As you can't propagate upward a change of variables, you have to "replay" the output kindly generated per WinpythonIni.py |
|
Where did the functionality of |
|
Env.ini is to not have to regenerate the env.bat every release . Whatever small things that can trouble an anti virus |
|
So why is |
|
Hu ? Hummm, did I forgot to force generate it at first icon click ? |
|
apparently i did remove the "useless otherwise" call to get that winpython.ini generated per winpythonini.py. so until you try an icon, it's not created ... someone has to find where that overkill broomstick gesture happened |
|
before summer 2024 settings/winpython.ini was created if empty per env.bat |
I finally figured out that
winpython.iniis actually handled inenv_for_icons.bat, not env.batand that it is converted into commands that are executed from within that batch file that do things like setting environment variables, so that's why nothing inwinpython.ini` was having any effect.