Nick Coghlan wrote:
> However, the scoping of for loop
> variables won't change, as the current behaviour is essential for search
> loops
> that use a break statement to terminate the loop when the item is found.
It occurs to me that there's a middle ground here:
leave the loop variable scope
Ben Wing wrote:
> apologies if this has been brought up on python-dev already.
>
> a suggestion i have, perhaps for python 3.0 since it may break some code
> (but imo it could go into 2.6 or 2.7 because the likely breakage would
> be very small, see below), is the elimination of the misfeature w
