[issue16429] Emit SyntaxWarning for code that risks UnboundLocalError

2017-03-07 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue16429] Emit SyntaxWarning for code that risks UnboundLocalError

2014-10-06 Thread Georg Brandl
Georg Brandl added the comment: I seem to recall that this was rejected into the realm of linters in a python-dev discussion. If there is a chance of false positives, having Python emit the warning would be annoying because there is no convenient way of telling it to shut up about it. At lea

[issue16429] Emit SyntaxWarning for code that risks UnboundLocalError

2014-08-03 Thread Mark Lawrence
Changes by Mark Lawrence : -- type: -> enhancement versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mail

[issue16429] Emit SyntaxWarning for code that risks UnboundLocalError

2013-05-04 Thread Daniel Urban
Changes by Daniel Urban : -- nosy: +daniel.urban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue16429] Emit SyntaxWarning for code that risks UnboundLocalError

2012-11-15 Thread Andrew Svetlov
Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue16429] Emit SyntaxWarning for code that risks UnboundLocalError

2012-11-07 Thread Nick Coghlan
New submission from Nick Coghlan: The compiler is actually in a fairly good position to tell when code is at risk of triggering UnboundLocalError at runtime: specifically, in the section of the code that checks for duplicated parameter names [1] Now, we can't emit SyntaxError here for backward