Ezio Melotti added the comment: Fixed, thanks for the patch! However I had to change a couple of things: 1) test_main contained c/py_warnings.onceregistry.clear(), and removing that breaks when running the test twice in a row. I now added it to setUpModule, and that seems to be called both when the tests are run via regrtest and also when they are run via unittest. 2) Since the onceregistry wasn't cleared at the end of the tests, I also added a tearDownModule to take care of it. 3) I reorganized a bit the inheritance trees of the classes because they were inconsistent. Now all the tests use BaseTest -> TestFoo(BaseTest) -> C/PyTestFoo(TestFoo, Unittest). Previously some of the tests used BaseTest | TestFoo -> C/PyTestFoo(BaseTest, TestFoo, Unittest).
---------- assignee: -> ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16905> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
