This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yselivanov
Recipients martius, ned.deily, r.david.murray, vstinner, yselivanov
Date 2016-11-23.21:40:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479937208.51.0.176466790047.issue28782@psf.upfronthosting.co.za>
In-reply-to
Content
Wow, Martin, this is a very interesting one.  Thanks so much for tracking this down and reducing the test case.

So far this doesn't seem to be related to async/await: the interpreter stack seems to enter some strange state under some conditions, and async/await just happens to be the thing that explodes.

To those trying to debug this: you don't need asyncio, just replace `loop.run_until_complete(main())` with `main().send(None)`.
History
Date User Action Args
2016-11-23 21:40:08yselivanovsetrecipients: + yselivanov, vstinner, ned.deily, r.david.murray, martius
2016-11-23 21:40:08yselivanovsetmessageid: <1479937208.51.0.176466790047.issue28782@psf.upfronthosting.co.za>
2016-11-23 21:40:08yselivanovlinkissue28782 messages
2016-11-23 21:40:08yselivanovcreate