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 martin.panter
Recipients docs@python, gvanrossum, martin.panter, paul.moore
Date 2015-06-15.23:39:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1434411588.78.0.5893234948.issue24087@psf.upfronthosting.co.za>
In-reply-to
Content
Okay. The biggest thing that concerns me at the moment to do with the term is that there are too many related but different, specific meanings, that I suspect could be confusing, including:

1. Generators (and presumably also the new “async” native coroutines), compatible with “asyncio”: <https://docs.python.org/3.5/library/asyncio-task.html#coroutines>

2. PEP 492 “native” coroutines: <https://docs.python.org/3.5/glossary.html#term-coroutine-function>

Okay maybe some of the new wording is not needed any more. I plan to try documenting some basic stuff about the new PEP 492 coroutines in Issue 24439. Maybe I will incorporate the “native coroutine” clarifications from my patch here at the same time.
History
Date User Action Args
2015-06-15 23:39:48martin.pantersetrecipients: + martin.panter, gvanrossum, paul.moore, docs@python
2015-06-15 23:39:48martin.pantersetmessageid: <1434411588.78.0.5893234948.issue24087@psf.upfronthosting.co.za>
2015-06-15 23:39:48martin.panterlinkissue24087 messages
2015-06-15 23:39:48martin.pantercreate