Comment 1 for bug 1408774

Indeed. The problem is I haven't been able to think of a way to do that which doesn't also catch legitimate use cases.

This was discussed recently on the code-quality mailing list. Archive here: https://mail.python.org/pipermail/code-quality/2014-December/000450.html

Can you think of some logic that would catch the problem in your example, but not also apply to at least some of the use cases enumerated in that thread, thus generating false positives?