[issue33776] Segfault when passing invalid argument to asyncio.ensure_future

Yury Selivanov added the comment: Thanks for reporting it. Looks like this has been fixed in 3.6 (not yet released) and 3.7.0b5 in issue 33584. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue33776] Segfault when passing invalid argument to asyncio.ensure_future

New submission from Jason McKellar : If time.monotonic() is yielded from a generator that is passed to asyncio.ensure_future a segfault occurs when it's scheduled. The example below shows time.monotonic called in the generator, however the segfault will also occur if a function is called (no