[issue25695] test___all__ and test_support alter execution environment

Martin Panter added the comment: This should be fixed now. Thanks for the report Arfrever and the analysis Ghost. I still get these warnings, but they are discussed in Issue 18383: Warning -- warnings.filters was modified by test___all__ Warning -- warnings.filters was modified by test_warnings

[issue25695] test___all__ and test_support alter execution environment

Roundup Robot added the comment: New changeset fb72d6d7703c by Martin Panter in branch 'default': Issue #25695: Defer creation of TESTDIRN until the test case is run https://hg.python.org/cpython/rev/fb72d6d7703c -- nosy: +python-dev ___ Python tracke

[issue25695] test___all__ and test_support alter execution environment

Serhiy Storchaka added the comment: defer-TESTDIRN.patch LGTM. -- nosy: +serhiy.storchaka stage: patch review -> commit review ___ Python tracker ___

[issue25695] test___all__ and test_support alter execution environment

Martin Panter added the comment: This was introduced with revision f8fa7bc837a3. I guess I overlooked the new messages because I run the tests with -Wall, which is affected by Issue 18383. It seems a bad idea to create a temporary directory when you import the test_support module. I propose th

[issue25695] test___all__ and test_support alter execution environment

SilentGhost added the comment: test_support has this line: TESTDIRN = os.path.basename(tempfile.mkdtemp(dir='.')) Which is the culprit. The reason it gets so far as to import the module is due to the "fuzzy logic" check looking for __all__ What I'd suggest is replacing simple "in" string sear

[issue25695] test___all__ and test_support alter execution environment

New submission from Arfrever Frehtes Taifersar Arahesis: test___all__ and test_support alter execution environment. Problem seems to be present only in Python 3.6. $ python3.5 -m test test___all__ test_support [1/2] test___all__ [2/2] test_support All 2 tests OK. $ python3.6 -m test test___all__