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 GeeTransit
Recipients GeeTransit, Joshua Oreman, ZackerySpytz, asvetlov, dabeaz, giampaolo.rodola, kdart, njs, xgdomingo, yarkot, yselivanov
Date 2019-08-08.22:49:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565304560.0.0.250611931116.issue32810@roundup.psfhosted.org>
In-reply-to
Content
Also, while the PEP first introducing asynchronous generators stated that its .asend() and .athrow() methods will return a "coroutine-like object", it doesn't allow any introspection into its state or parent async generator.

My workaround was to wrap the .asend() and other methods with another coroutine that just awaits and returns the result. Having a better way to check its state and frame will bring it closer to a coroutine.
History
Date User Action Args
2019-08-08 22:49:20GeeTransitsetrecipients: + GeeTransit, kdart, giampaolo.rodola, yarkot, njs, asvetlov, dabeaz, yselivanov, xgdomingo, ZackerySpytz, Joshua Oreman
2019-08-08 22:49:19GeeTransitsetmessageid: <1565304560.0.0.250611931116.issue32810@roundup.psfhosted.org>
2019-08-08 22:49:19GeeTransitlinkissue32810 messages
2019-08-08 22:49:19GeeTransitcreate