STINNER Victor added the comment:
I'm sorry, but I'm not interested anymore to work on asyncio, and I'm unable to
say if the bug was fixed since I reported it or not :-/ But I saw work on
cancellation. So maybe it was already fixed. I now just close the issue.
--
resolution: -> out of
New submission from STINNER Victor:
I noticed the following warning in test_asyncio (see above). It understand that
when the asyncio Future ("destination" in _chain_future) is cancelled,
_call_check_cancel() calls source_loop.call_soon_threadsafe(source.cancel)
where source is a concurrent.fut
