On Nov 21, 2014, at 10:55 PM, Nick Coghlan wrote:
I suspect enough evidence of breakage is accumulating to tip the balance back to "not worth the hassle", but it would also be possible to just *add* the "from __future__ import generator_stop" feature, and postpone a decision on making that the only available behaviour.
I have no opinion on the actual PEP, but I'm not sure the above is a good resolution. future imports should be for things that have a clear path to default behavior in some future release. I don't think we should incur technical debt to future-ize a feature that won't eventually get adopted. Such a thing will just be another wart that will be difficult to remove for backward compatibility.