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 ncoghlan, syncosmic
Date 2017-08-18.03:00:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A related issue (since this issue is contemplating restructuring these objects anyway):

Other than `??_code`, none of the `f.func_X` attributes which were eliminated in 3.0 have direct equivalents in generator-iterators, coroutines, or async generator-iterators.

However, all three of those have `[gi|cr|ag]_running` and `[gi|cr|ag]_frame` attributes. Generator-iterators also have `gi_yieldfrom`, and coroutines and async generator-iterators have `[cr|ag]_await`.

On a clean slate (with no attention paid to issues around breaking changes or how these attributes are already used in existing code), is there an argument for dundering some or all of these along with `__code__`? Or is special casing a better pattern when dealing with these other attributes?
Date User Action Args
2017-08-18 03:00:41syncosmicsetrecipients: + syncosmic, ncoghlan
2017-08-18 03:00:41syncosmicsetmessageid: <>
2017-08-18 03:00:41syncosmiclinkissue31230 messages
2017-08-18 03:00:41syncosmiccreate