bpo-45238: Fix unittest.IsolatedAsyncioTestCase.debug()#28449
Conversation
It runs now asynchronous methods and callbacks. If it fails, doCleanups() can be called for cleaning up.
| def __del__(self): | ||
| if self._asyncioTestLoop is not None: | ||
| self._tearDownAsyncioLoop() |
There was a problem hiding this comment.
Looks a little weird but I don't have better idea.
There was a problem hiding this comment.
Yes, it looks very weird. And you should ensure that the IsolatedAsyncioTestCase instance is destroyed before any other event loop is run, otherwise you can get an ugly message on the stderr during garbage collecting.
|
Thanks @serhiy-storchaka for the PR, and @ambv for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10. |
|
Sorry @serhiy-storchaka and @ambv, I had trouble checking out the |
|
Sorry, @serhiy-storchaka and @ambv, I could not cleanly backport this to |
|
Thanks @serhiy-storchaka for the PR, and @ambv for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
|
Sorry @serhiy-storchaka and @ambv, I had trouble checking out the |
|
whyyy |
…nGH-28449) It runs now asynchronous methods and callbacks. If it fails, doCleanups() can be called for cleaning up. (cherry picked from commit ecb6922) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
GH-28521 is a backport of this pull request to the 3.10 branch. |
|
GH-28522 is a backport of this pull request to the 3.9 branch. |
|
|
It runs now asynchronous methods and callbacks.
If it fails, doCleanups() can be called for cleaning up.
https://bugs.python.org/issue45238