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 yselivanov
Recipients Eric Appelt, gvanrossum, ncoghlan, ned.deily, yselivanov
Date 2016-12-09.22:04:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481321052.49.0.1619052604.issue28091@psf.upfronthosting.co.za>
In-reply-to
Content
> It sounds particularly confusing that an "[XXX] generator" is the function
in one case and the object in the other case.

Right, this is the biggest argument against having slightly different terminology between async generators and sync generators.

Maybe we should update docs for synchronous generators and replace "generator" with "generator function" and "generator iterable" with "generator"?

Most of the existing documentation refers to generator objects when the term "generator" is used anyways.

> There's of course also Nathaniel Smith's opinion that we should switch away
from the term coroutine and call those "async def". Is that relevant?

IIRC he's advocating to refer to "coroutine functions" as "async functions" and to "coroutines" as "async something". I personally don't buy his arguments and think that the current terminology is good and people already seem to understand/like it.
History
Date User Action Args
2016-12-09 22:04:12yselivanovsetrecipients: + yselivanov, gvanrossum, ncoghlan, ned.deily, Eric Appelt
2016-12-09 22:04:12yselivanovsetmessageid: <1481321052.49.0.1619052604.issue28091@psf.upfronthosting.co.za>
2016-12-09 22:04:12yselivanovlinkissue28091 messages
2016-12-09 22:04:12yselivanovcreate