[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2015-03-18 Thread STINNER Victor
STINNER Victor added the comment: There is a single test which uses __cleanenv=True: test_hash. The test pass on Windows and this issue is old. I prefer to simplify close it. -- resolution: - out of date status: open - closed ___ Python tracker

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-16 Thread STINNER Victor
STINNER Victor added the comment: Serhiy Interesting, how isolation mode works on Windows or if Python is compiled in shared module? Should we keep these environment variables if the __isolated keyword is used? The __isolated parameter of script_helper._assert_python() don't start Python

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-16 Thread Brian Curtin
Changes by Brian Curtin br...@python.org: -- nosy: -brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20614 ___ ___ Python-bugs-list

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-15 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Interesting, how isolation mode works on Windows or if Python is compiled in shared module? Should we keep these environment variables if the __isolated keyword is used? -- ___ Python tracker

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-15 Thread Arfrever Frehtes Taifersar Arahesis
Arfrever Frehtes Taifersar Arahesis added the comment: Oh, another problem: if Python is compiled in shared module, libpython3.4.so cannot be found. LD_LIBRARY_PATH must also be copied if __cleanenv=True. Py_ENABLE_SHARED can be checked in sysconfig to decide if the environment variable

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-13 Thread STINNER Victor
New submission from STINNER Victor: On Windows, if Python is started with an empty environment (no environment variable at all), Python fails with: Fatal Python error: Failed to initialize Windows random API (CryptoGen) It's the Windows error 0x80090006 which is not displayed in the error

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-13 Thread STINNER Victor
STINNER Victor added the comment: cleanenv.patch: untested test. -- keywords: +patch Added file: http://bugs.python.org/file34066/cleanenv.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20614

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-13 Thread STINNER Victor
STINNER Victor added the comment: When Python is executed in an empty environement, not only it displays Fatal Python error: Failed to initialize Windows random API (CryptoGen), but it opens also the fatal error popup on Windows. The issue #19983 proposes a patch to not abort() at exit, but

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-13 Thread STINNER Victor
STINNER Victor added the comment: Oh, another problem: if Python is compiled in shared module, libpython3.4.so cannot be found. LD_LIBRARY_PATH must also be copied if __cleanenv=True. Py_ENABLE_SHARED can be checked in sysconfig to decide if the environment variable should be copied or not.

[issue20614] test.script_helper should copy SYSTEMROOT environment variable for __cleanenv=True

2014-02-13 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20614 ___ ___