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 vstinner
Recipients SzieberthAdam, gvanrossum, pitrou, python-dev, r.david.murray, vstinner, yselivanov
Date 2014-06-16.14:20:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ok, this issue is now fixed in Python 3.5.

For Python 2.7 and 3.4, it may be possible to change how the generator name is set (from the function, not from the code object). It might break the backward compatibility, even if I don't think that anyone rely on the exact name of the generator, and the function name is more useful than the code name.

What do you think for Python 2.7 and 3.4: would you be ok to change also the generator name? I can write a patch which adds a new gi_name but the name would not be modifiable to limit the incompatible changes.
Date User Action Args
2014-06-16 14:20:06vstinnersetrecipients: + vstinner, gvanrossum, pitrou, r.david.murray, python-dev, yselivanov, SzieberthAdam
2014-06-16 14:20:06vstinnersetmessageid: <>
2014-06-16 14:20:06vstinnerlinkissue21205 messages
2014-06-16 14:20:06vstinnercreate