bpo-43913: Fix bugs in cleaning up classes and modules in unittest. #28006
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Functions registered with addModuleCleanup() were not called unless the user defines tearDownModule() in their test module. * Functions registered with addClassCleanup() were not called if tearDownClass is set to None. * Buffering in TestResult did not work with functions registered with addClassCleanup() and addModuleCleanup(). * Errors in functions registered with addClassCleanup() and addModuleCleanup() were not handled correctly in buffered and debug modes. * Errors in setUpModule() and functions registered with addModuleCleanup() were reported in wrong order. * And several lesser bugs.
ambv
reviewed
Aug 30, 2021
|
Thanks @serhiy-storchaka for the PR, and @ambv for merging it |
miss-islington
added a commit
to miss-islington/cpython
that referenced
this issue
Aug 30, 2021
…ythonGH-28006) * Functions registered with addModuleCleanup() were not called unless the user defines tearDownModule() in their test module. * Functions registered with addClassCleanup() were not called if tearDownClass is set to None. * Buffering in TestResult did not work with functions registered with addClassCleanup() and addModuleCleanup(). * Errors in functions registered with addClassCleanup() and addModuleCleanup() were not handled correctly in buffered and debug modes. * Errors in setUpModule() and functions registered with addModuleCleanup() were reported in wrong order. * And several lesser bugs. (cherry picked from commit 08d9e59) Co-authored-by: Serhiy Storchaka <[email protected]>
|
Sorry, @serhiy-storchaka and @ambv, I could not cleanly backport this to |
|
GH-28070 is a backport of this pull request to the 3.10 branch. |
|
Thanks @serhiy-storchaka for the PR, and @ambv for merging it |
|
Sorry @serhiy-storchaka and @ambv, I had trouble checking out the |
|
@serhiy-storchaka I'm fixing the conflict for 3.9. |
|
GH-28071 is a backport of this pull request to the 3.9 branch. |
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this issue
Aug 30, 2021
…est. (pythonGH-28006) * Functions registered with addModuleCleanup() were not called unless the user defines tearDownModule() in their test module. * Functions registered with addClassCleanup() were not called if tearDownClass is set to None. * Buffering in TestResult did not work with functions registered with addClassCleanup() and addModuleCleanup(). * Errors in functions registered with addClassCleanup() and addModuleCleanup() were not handled correctly in buffered and debug modes. * Errors in setUpModule() and functions registered with addModuleCleanup() were reported in wrong order. * And several lesser bugs.. (cherry picked from commit 08d9e59) Co-authored-by: Serhiy Storchaka <[email protected]>
ambv
added a commit
to ambv/cpython
that referenced
this issue
Aug 30, 2021
…est. (pythonGH-28006) * Functions registered with addModuleCleanup() were not called unless the user defines tearDownModule() in their test module. * Functions registered with addClassCleanup() were not called if tearDownClass is set to None. * Buffering in TestResult did not work with functions registered with addClassCleanup() and addModuleCleanup(). * Errors in functions registered with addClassCleanup() and addModuleCleanup() were not handled correctly in buffered and debug modes. * Errors in setUpModule() and functions registered with addModuleCleanup() were reported in wrong order. * And several lesser bugs.. (cherry picked from commit 08d9e59) Co-authored-by: Serhiy Storchaka <[email protected]>
ambv
pushed a commit
that referenced
this issue
Aug 30, 2021
…est. (GH-28006) (GH-28071) * Functions registered with addModuleCleanup() were not called unless the user defines tearDownModule() in their test module. * Functions registered with addClassCleanup() were not called if tearDownClass is set to None. * Buffering in TestResult did not work with functions registered with addClassCleanup() and addModuleCleanup(). * Errors in functions registered with addClassCleanup() and addModuleCleanup() were not handled correctly in buffered and debug modes. * Errors in setUpModule() and functions registered with addModuleCleanup() were reported in wrong order. * And several lesser bugs.. (cherry picked from commit 08d9e59) Co-authored-by: Serhiy Storchaka <[email protected]>
miss-islington
added a commit
that referenced
this issue
Aug 30, 2021
…H-28006) * Functions registered with addModuleCleanup() were not called unless the user defines tearDownModule() in their test module. * Functions registered with addClassCleanup() were not called if tearDownClass is set to None. * Buffering in TestResult did not work with functions registered with addClassCleanup() and addModuleCleanup(). * Errors in functions registered with addClassCleanup() and addModuleCleanup() were not handled correctly in buffered and debug modes. * Errors in setUpModule() and functions registered with addModuleCleanup() were reported in wrong order. * And several lesser bugs. (cherry picked from commit 08d9e59) Co-authored-by: Serhiy Storchaka <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
the user defines tearDownModule() in their test module.
tearDownClass is set to None.
with addClassCleanup() and addModuleCleanup().
addModuleCleanup() were not handled correctly in buffered and
debug modes.
addModuleCleanup() were reported in wrong order.
https://bugs.python.org/issue43913
The text was updated successfully, but these errors were encountered: