You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally reported by: BitBucket: gpshead, GitHub: @gpshead?
I've seen some code use this, but it is exceedingly rare from what I can tell:
"""Test some style nits vs pylint."""from __future__ importprint_functiontry:
passexcept(IOError, KeyError) aserror:
print(error)
It'd be nice to tell users to always put a space between an except and any following ( in the case of a tuple of exceptions being specified.
In our internal code base I found around ~0.3% of except clauses with a tuple do this (tiny!).
In a bunch of open source code I've grepped over, pandas has one unittest (test_ujson.py) that repeats this pattern, numpy's fft/fftpack.py does it once. It really is not common.
Originally reported by: BitBucket: gpshead, GitHub: @gpshead?
I've seen some code use this, but it is exceedingly rare from what I can tell:
It'd be nice to tell users to always put a space between an except and any following ( in the case of a tuple of exceptions being specified.
In our internal code base I found around ~0.3% of except clauses with a tuple do this (tiny!).
In a bunch of open source code I've grepped over, pandas has one unittest (test_ujson.py) that repeats this pattern, numpy's fft/fftpack.py does it once. It really is not common.
The text was updated successfully, but these errors were encountered: