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 | chris.jerdonek |
|---|---|
| Recipients | chris.jerdonek, docs@python, ncoghlan, terry.reedy |
| Date | 2012年07月28日.01:44:59 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1343439903.28.0.855329979378.issue15457@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Attaching updated patch incorporating feedback. It would be nice to have a good term for "the generator function code object associated with a generator" to distinguish it from the original generator function as you point out. There are many places in the docs where this distinction is blurred, for example throughout the subsection describing generator methods: "generator.__next__(): Starts the execution of a generator function or resumes it at the last executed yield expression..." http://docs.python.org/dev/reference/expressions.html#generator.__next__ By the way, I think it would be a good idea to add "code object" to the glossary as it is not currently listed. In particular, the entry could link to the section of the docs that discuss code objects in more detail: http://docs.python.org/reference/datamodel.html#the-standard-type-hierarchy specifically: http://docs.python.org/dev/reference/datamodel.html#index-52 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年07月28日 01:45:03 | chris.jerdonek | set | recipients: + chris.jerdonek, terry.reedy, ncoghlan, docs@python |
| 2012年07月28日 01:45:03 | chris.jerdonek | set | messageid: <1343439903.28.0.855329979378.issue15457@psf.upfronthosting.co.za> |
| 2012年07月28日 01:45:02 | chris.jerdonek | link | issue15457 messages |
| 2012年07月28日 01:45:02 | chris.jerdonek | create | |