[issue4992] yield's documentation not updated

[Georg Brandl]

Georg Brandl ge...@python.org added the comment:

Thanks, fixed in r69294.

--
resolution:  - fixed
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4992
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4992] yield's documentation not updated

[Terry J. Reedy]

Terry J. Reedy tjre...@udel.edu added the comment:

I would go with the first suggestion as that was the intent of adding
next() as a builtin function.

--
nosy: +tjreedy

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4992
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4992] yield's documentation not updated

[Petr Viktorin]

New submission from Petr Viktorin encu...@gmail.com:

In the yield statement documentation
(http://docs.python.org/3.0/reference/simple_stmts.html#the-yield-statement),
the old way of calling generators is used:

The body of the generator function is executed by calling the
generator’s next() method repeatedly until it raises an exception.

This should be changed to something like:

The body of the generator function is executed by calling the next()
function on the generator repeatedly until it raises an exception.

Or just replace next() with __next__(), and fix the next paragraph as well.

--
assignee: georg.brandl
components: Documentation
messages: 80134
nosy: En-Cu-Kou, georg.brandl
severity: normal
status: open
title: yield's documentation not updated
versions: Python 3.0

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4992
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com