[issue6580] No deprecation warning for list comprehension leak conflict

Terry J. Reedy added the comment: Not an issue in 3.x. -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Py

[issue6580] No deprecation warning for list comprehension leak conflict

Terry J. Reedy added the comment: 2.5 is closed to fixes other than security fixes. So this needs to be checked with the latest 2.6. The implementation of new features does not always exactly follow the PEP. So if there is also no warning in 2.6, the question remains whether accident or intenti

[issue6580] No deprecation warning for list comprehension leak conflict

New submission from Michael R Bax : PEP 289 states that "Python 2.4 and beyond should issue a deprecation warning if a list comprehension's loop variable has the same name as a variable used in the immediately surrounding scope". But no warning is shown when running for x in [ 0 ]: print