[issue12401] unset PYTHON* environment variables when running tests

STINNER Victor added the comment: > 1. Fix the tests that might be affected by such problems, by adding the -E > option everywhere needed. Yes, this is the right fix. I'm closing this issue because it didn't get any activity since 3 years. If you are interested to add -E in tests, please open

[issue12401] unset PYTHON* environment variables when running tests

Mark Lawrence added the comment: Can we have a formal patch review please as "make test" means nothing to me. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker _

[issue12401] unset PYTHON* environment variables when running tests

Changes by Ezio Melotti : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue12401] unset PYTHON* environment variables when running tests

Changes by Terry J. Reedy : -- nosy: +ezio.melotti, michael.foord ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue12401] unset PYTHON* environment variables when running tests

Henry Precheur added the comment: Here's a small patch to call regression tests without any environment variable defined. It's probably a good thing to run all the tests with a clean state, this way they are less likely to fail for mysterious external reasons. For example test_displayhook_une

[issue12401] unset PYTHON* environment variables when running tests

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue12401] unset PYTHON* environment variables when running tests

New submission from Henry Precheur : "make test" calls Python with the -E option which ignore the PYTHON* environment variables, but Python sub-processes aren't necessarily called with the -E options. For example test_displayhook_unencodable in test_cmd_line. This created problems with my own P