Chris Jerdonek added the comment:
Terry, if when reviewing my patch for issue 15457, you also have time to review
this much simpler patch (also in the documentation on generators), I would
appreciate it. If not, that's okay.
--
nosy: +terry.reedy
Meador Inge added the comment:
Hmmm, in your original description you say that the 'generator.__next__'
documentation should be changed, but in the patch the note applies to all
generator methods. From looking at the code it seems that the patch is correct
and that '__next__', 'send',
Chris Jerdonek chris.jerdo...@gmail.com added the comment:
This is a very simple patch.
--
keywords: +patch
Added file: http://bugs.python.org/file26525/issue-15355-1.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15355
Changes by Chris Jerdonek chris.jerdo...@gmail.com:
--
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15355
___
___
Changes by Nick Coghlan ncogh...@gmail.com:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15355
___
___
Python-bugs-list
New submission from Chris Jerdonek chris.jerdo...@gmail.com:
I think the generator.__next__() documentation should say that it raises an
exception if the generator is already executing:
http://docs.python.org/dev/reference/expressions.html#generator.__next__
I don't think this is currently
