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 syncosmic
Recipients Mariatta, ncoghlan, serhiy.storchaka, syncosmic
Date 2017-08-12.10:39:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502534357.91.0.291893501698.issue31183@psf.upfronthosting.co.za>
In-reply-to
Content
Hm--either/both? I encountered it as a bug ("dis works on my generator object and my async generator function, why does it break on my async generator object?") but strictly speaking it's a new feature (just as issue21947 was). To my mind, adding this level of indirection (finding the code object) for generators was a bit of a design decision but once it's in for generators it should be in for async generators and coroutines by analogy.
History
Date User Action Args
2017-08-12 10:39:17syncosmicsetrecipients: + syncosmic, ncoghlan, serhiy.storchaka, Mariatta
2017-08-12 10:39:17syncosmicsetmessageid: <1502534357.91.0.291893501698.issue31183@psf.upfronthosting.co.za>
2017-08-12 10:39:17syncosmiclinkissue31183 messages
2017-08-12 10:39:17syncosmiccreate