STINNER Victor added the comment:
A lot of fixes has been commited to fix this general issue with asyncio at exit.
run_until_complete() doesn't log an error anymore when a BaseException (like
KeyboardInterrupted) is raised. The caller is able to decide how to handle it.
The traceback module
STINNER Victor added the comment:
= IMO it's an issue in the traceback module. It may catch the AttributeError
on the call to linecache.getline().
I created the issue #22599 for this bug.
--
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
If the coroutine raises an exception which doesn't inherit from Exception
(but inherits from BaseException), run_until_complete() doesn't consume the
exception from the temporary task object
I created the issue #22601 for this bug.
--
STINNER Victor added the comment:
The issue #22480 has been marked as a duplicate of this issue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22428
___
Changes by STINNER Victor victor.stin...@gmail.com:
--
title: KeyboardInterrupt inside a coroutine causes AttributeError - asyncio:
KeyboardInterrupt inside a coroutine causes AttributeError
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
I see different issues in your example:
* If the coroutine raises an exception which doesn't inherit from Exception
(but inherits from BaseException), run_until_complete() doesn't consume the
exception from the temporary task object
=
