[issue30083] Asyncio: GeneratorExit + strange exception

Guilherme Salgado added the comment: I've also been affected by this and found that if you use asyncio.run() the coroutine is interrupted with a CancelledError as you'd expect. The following script shows that === import asyncio async def handle_connection(reader, writer

[issue39116] StreamReader.readexactly() raises GeneratorExit on ProactorEventLoop

Change by Guilherme Salgado : -- nosy: +salgado ___ Python tracker <https://bugs.python.org/issue39116> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40152] Coroutine hangs if it performs async operations when handling exception sent using throw()

Change by Guilherme Salgado : -- versions: +Python 3.8 ___ Python tracker <https://bugs.python.org/issue40152> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40152] Coroutine hangs if it performs async operations when handling exception sent using throw()

New submission from Guilherme Salgado : A coroutine will hang forever if it that catches an exception sent via its throw() method and then makes async calls while handling that exception. The same coroutine will complete just fine if the exception is instead raised from within it. Here's

[issue34098] multiprocessing.Server swallows original exception traceback

New submission from Guilherme Salgado : multiprocessing.Server swallows original exception traceback, making it hard to debug. For example, the following code: ``` from multiprocessing.managers import BaseManager class FooBar(object): def m(self): self._raise() def _raise

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Guilherme Salgado gsalg...@gmail.com: -- nosy: -salgado ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Guilherme Salgado gsalg...@gmail.com: -- nosy: +salgado ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list