1
92%
main: 95%

Ran 23 Aug 2016 05:51AM UTC

Files 52

Run time 2s

Badge

Embed ▾

Committed 23 Aug 2016 05:46AM UTC coverage: 88.949%. Remained the same

Job # TOXENV=py27

Build Type

push

travis-ci

Committed by

PCManticore

Commit Message

Don't warn about used-before-assignment if the variable is in an exclusive except branch with NameError as a handler

Until now, we weren't emitting a warning in the case of a variable being
referenced before actual definition, with the variable access being placed
inside a TryExcept, with an except handler that caught NameError, Exception and BaseException.
While for NameError it makes sense, since it is explicit that the user is expecting
a variable to not be defined, it does not make that much sense for the rest of
the exceptions, even if they are supertypes of NameError anyway. This is because
it is not explicit and we cannot infer what the user intended to do anyway.
We are now only handling NameError.

Close #1080

Run Details

8749 of 9836 relevant lines covered (88.95%)

0.89 hits per line

PyCQA / pylint / 702 / 1
92%
main: 95%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 702.1 (TOXENV=py27)

PyCQA / pylint / 702 / 1 92% main: 95%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 702.1 (TOXENV=py27)

PyCQA / pylint / 702 / 1
92%
main: 95%

README BADGES
x