Detect misuse of except
Bug #848455 reported by
Tristan Seligmann
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Pyflakes |
New
|
Wishlist
|
Unassigned | ||
| pyflakes (Debian) |
Confirmed
|
Unknown
|
|||
Bug Description
It would be nice if pyflakes could detect mistakes like this:
try:
oldtime = os.path.
except OSError, IOError:
oldtime = 0
In the general case, it's obviously difficult to tell whether this is an error or not; but I suspect that handling the exception variable name as a binding would give you a "redefinition of Foo" warning in most of the cases where a mistake has been made.
| Changed in pyflakes: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Jean-Paul Calderone (exarkun) wrote | #1 |
| Changed in pyflakes (Debian): | |
| status: | Unknown → New |
| Changed in pyflakes (Debian): | |
| status: | New → Confirmed |
Revision history for this message
| Wilfred Hughes (yatc18ks0-9a-ngeefk4xa) wrote | #2 |
Revision history for this message
| Tristan Seligmann (mithrandi) wrote | #3 |
Revision history for this message
| Marcin Cieślak (saperski) wrote | #4 |
| Changed in pyflakes: | |
| status: | New → Fix Released |
Revision history for this message
| Marcin Cieślak (saperski) wrote | #5 |
| Changed in pyflakes: | |
| status: | Fix Released → New |
To post a comment you must log in.
Sounds reasonable. At least it would be interesting to run such a check against existing codebases to see what comes up. :)