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 ncoghlan
Recipients ncoghlan
Date 2015-05-19.11:16:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432034180.53.0.39436182939.issue24237@psf.upfronthosting.co.za>
In-reply-to
Content
From the StopIteration-in-generators handling transition plan (https://www.python.org/dev/peps/pep-0479/#transition-plan):

* Python 3.5: Enable new semantics under __future__ import; silent deprecation warning if StopIteration bubbles out of a generator not under __future__ import. 

The first half of that was implemented in issue 22906, but we missed the second half.

The reason the latter is needed is so that people can turn the DeprecationWarning into an error to test for compatibility with the future default behaviour without needing to add the new future flag to their code (which would break compatibility with older Python versions). Ram Rachum pointed out the absence on python-ideas: https://mail.python.org/pipermail/python-ideas/2015-May/033580.html
History
Date User Action Args
2015-05-19 11:16:20ncoghlansetrecipients: + ncoghlan
2015-05-19 11:16:20ncoghlansetmessageid: <1432034180.53.0.39436182939.issue24237@psf.upfronthosting.co.za>
2015-05-19 11:16:20ncoghlanlinkissue24237 messages
2015-05-19 11:16:20ncoghlancreate