[Python-Dev] variable name resolution in exec is incorrect

Terry Reedy tjreedy at udel.edu
Mon May 31 01:55:31 CEST 2010


On 5/29/2010 6:20 AM, Colin H wrote:
> Perhaps the next step is to re-open the issue? If it is seen as a bug,
> it would be great to see a fix in 2.6+ -

For the purpose of bugfix releases, a 'bug' is a discrepancy between doc 
and behavior. Every new feature is seen as a 'design bug' by someone.

 > a number of options which
> will not break backward compatibility have been put forward - cheers,

Code that uses a new x.y.z feature does not work in previous x.y 
versions. Problems with such micro-release additions lead to the current 
policy.

The 3.2 feature addition deadline is about 5 months away. It will 
probably take 1 or more people at least a couple of months to write a 
PEP listing the rationale for a change, the options and possible pros 
and cons, possibly test one or more patches, solicit opinions on which 
is best, select one, write new test cases and docs, and get the final 
patch committed.

Terry Jan Reedy



More information about the Python-Dev mailing list