23 May
2014
23 May
'14
10:22 a.m.
On 24 May 2014 02:49, "Guido van Rossum"
I'm not happy with the direction this is taking. I would prefer an
approach that *first* implements the minimal thing (an internal flag, set by an environment variable, to disable the peephole optimizer) and *then* perhaps revisits the greater UI for specifying optimization levels and the consequences this has for pyc/pyo files. Sure, that sounds like a reasonable approach, too. My perspective is mainly coloured by the fact that we're still in the "eh, feature freeze is still more than a year away" low urgency period for 3.5 :) Cheers, Nick.