[issue33238] AssertionError on await of Future returned by asyncio.wrap_future

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue33238] AssertionError on await of Future returned by asyncio.wrap_future

Andrew Svetlov added the comment: New changeset 0a28c0d12ee7201de039ced4d815f57f1f8fd48c by Andrew Svetlov (jhaydaman) in branch 'master': bpo-33238: Add InvalidStateError to concurrent.futures. (GH-7056) https://github.com/python/cpython/commit/0a28c0d12ee7201de039ced4d815f57f1f8fd48c

[issue33238] AssertionError on await of Future returned by asyncio.wrap_future

Change by Jason Haydaman : -- keywords: +patch pull_requests: +6690 stage: -> patch review ___ Python tracker ___

[issue33238] AssertionError on await of Future returned by asyncio.wrap_future

Change by Andrew Svetlov : -- versions: +Python 3.8 -Python 3.6 ___ Python tracker ___

[issue33238] AssertionError on await of Future returned by asyncio.wrap_future

Andrew Svetlov added the comment: Raising `InvalidStateError` sounds perfect. Would you make a pull request? -- ___ Python tracker

[issue33238] AssertionError on await of Future returned by asyncio.wrap_future

Jason Haydaman added the comment: May also be worth pointing out that even in the case of only calling set_result once, _done_callbacks still has _chain_future in it: import asyncio import concurrent.futures f = concurrent.futures.Future() async_f =

[issue33238] AssertionError on await of Future returned by asyncio.wrap_future

New submission from Jason Haydaman : When the concurrent Future wrapped by asyncio.wrap_future has set_result or set_exception called multiple times, I get the following traceback: Traceback (most recent call last): File