bpo-45924: Fix asyncio incorrect traceback when future's exception is raised multiple times (GH-30274)

This commit is contained in:
Kumar Aditya 2022-07-11 18:02:11 +05:30 committed by GitHub
parent f5b76330cf
commit 86c1df1872
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 47 additions and 2 deletions

View file

@ -1,13 +1,42 @@
# IsolatedAsyncioTestCase based tests
import asyncio
import traceback
import unittest
from asyncio import tasks
def tearDownModule():
asyncio.set_event_loop_policy(None)
class FutureTests(unittest.IsolatedAsyncioTestCase):
class FutureTests:
async def test_future_traceback(self):
async def raise_exc():
raise TypeError(42)
future = self.cls(raise_exc())
for _ in range(5):
try:
await future
except TypeError as e:
tb = ''.join(traceback.format_tb(e.__traceback__))
self.assertEqual(tb.count("await future"), 1)
else:
self.fail('TypeError was not raised')
@unittest.skipUnless(hasattr(tasks, '_CTask'),
'requires the C _asyncio module')
class CFutureTests(FutureTests, unittest.IsolatedAsyncioTestCase):
cls = tasks._CTask
class PyFutureTests(FutureTests, unittest.IsolatedAsyncioTestCase):
cls = tasks._PyTask
class FutureReprTests(unittest.IsolatedAsyncioTestCase):
async def test_recursive_repr_for_pending_tasks(self):
# The call crashes if the guard for recursive call
# in base_futures:_future_repr_info is absent