Serhiy Storchaka <storchaka+cpyt...@gmail.com> added the comment:
There is a design issue with the order of cleaning up. tearDown() is purposed to release resources acquired in setUp(). Resources acquired in test methods will be released in doCleanup() if use addCleanup(), but since doCleanup() is called after tearDown(), resources will be released not in reversed order of the time of acquiring. This causes issues if resources acquired in a test method depends on the resource acquired in setUp(). Adding doClassCleanups() and doModuleCleanups() with the same semantic will introduce this problem at class and module level. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue24412> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
