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 ncoghlan
Recipients Ben.Darnell, Yury.Selivanov, asvetlov, gvanrossum, martin.panter, ncoghlan, scoder, vstinner, yselivanov
Date 2015-06-20.08:03:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Based on that last comment, I realised there's something else @types.coroutine should now do: delegate both the existing gi_* attributes *and* the new cr_* attributes to the underlying generator.

That should allow all of the poking around in code object flags to be encapsulated entirely in the types module, as the 3 kinds of object would subsequently be distinguishable by their attributes:

    gi_running: generator-iterator or generator-as-coroutine
    cr_running: native coroutine or generator-as-coroutine
    both: generator-as-coroutine
Date User Action Args
2015-06-20 08:03:29ncoghlansetrecipients: + ncoghlan, gvanrossum, scoder, vstinner, asvetlov, Yury.Selivanov, Ben.Darnell, martin.panter, yselivanov
2015-06-20 08:03:29ncoghlansetmessageid: <>
2015-06-20 08:03:29ncoghlanlinkissue24400 messages
2015-06-20 08:03:29ncoghlancreate