Brett Cannon <br...@python.org> added the comment: OK, now that all the modules have been analyzed, let's see what is what.
The modules not playing nicely with others by blindly reseting the trace module: test_doctest test_pdb test_scope test_sys_settrace test_zipimport_support (because of test_doctest) And the tests failing because of recursion depth: test_exceptions test_pickle test_pickletools test_richcmp test_runpy And test_io is just special thanks to signals and threading. Here is my thinking on how to solve this. The tests that are not playing nicely with sys.settrace() should (a) be decorated with test.support.cpython_only, and (b) use addCleanup() to properly put the trace function back. For the recursion depth tests, either the cause (which is probably trace_trampoline()) needs to be analyzed to decide if some other semantics are needed or need something to unset the trace function and then put it back, but only if sys.gettrace() exists (e.g., don't block on non-CPython VMs). ---------- stage: needs patch -> _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10990> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
