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 Jim.Jewett
Recipients Jim.Jewett, docs@python, gvanrossum, r.david.murray, vstinner, yselivanov
Date 2015-05-04.14:10:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430748650.29.0.345720111007.issue24088@psf.upfronthosting.co.za>
In-reply-to
Content
OK, then how about

Current:
"""
When a generator function is called, it returns an iterator known as a generator. That generator then controls the execution of a generator function. The execution starts when one of the generator’s methods is called.
"""

Proposed:
"""
When a generator function is called, it does not complete its execution immediately.  Instead, it keeps its execution frame intact, and returns a special kind of iterator known as a generator. The iteration starts when one of the generator’s methods is called, and the generator executes within the existing generator frame, rather than creating a new one.
"""

This still seems to suggest that the generator uses the same frame as the generator function that created it; I was not aware that this was a guarantee.  (Reusing the same frame, yes.  Reusing that particular frame, no.)
History
Date User Action Args
2015-05-04 14:10:50Jim.Jewettsetrecipients: + Jim.Jewett, gvanrossum, vstinner, r.david.murray, docs@python, yselivanov
2015-05-04 14:10:50Jim.Jewettsetmessageid: <1430748650.29.0.345720111007.issue24088@psf.upfronthosting.co.za>
2015-05-04 14:10:50Jim.Jewettlinkissue24088 messages
2015-05-04 14:10:50Jim.Jewettcreate