On Tue, Nov 18, 2014 at 7:37 PM, Chris Angelico firstname.lastname@example.org wrote:
On Wed, Nov 19, 2014 at 1:56 PM, Guido van Rossum email@example.com wrote:
The only thing standing in the way of fixing this is the recognition that there may be a fair amount of code out there that depends on this hack,
which will have to be rewritten.
Has anyone come across any more non-trivial examples? We have contextlib (in the standard library) and contextlib2 (third-party), plus a number of StackOverflow posts and such. Are there any other known pieces of code that would be seriously hampered by this change?
One possible way to find out would be to write a simple version of a patch (maybe one that doesn't use __future__ but just always converts StopIteration to RuntimeError when it bubbling out of a generator frame) and run the stdlib tests, then see how many tests this breaks. (I understand if you don't want to write it. But maybe someone does. :-)