Project

General

Profile

Feature #385

Filter for pylint

Added by Rogers, Chris over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Testing
Target version:
Start date:
21 March 2011
Due date:
% Done:

100%

Estimated time:
Workflow:

Description

If we are to avoid drowning in a swamp of pylint "exceptions", we need to build a filter that allows us to explicitly say "I know this exception exists, but I want to pass anyway".


Related issues

Related to MAUS - Feature #386: Cpplint filterClosedRogers, Chris21 March 2011

Actions
#1

Updated by Tunnell, Christopher over 10 years ago

there is some pylint type string you can put to turn off certain types of errors. Or we could just diff errors to find new ones?

#2

Updated by Rogers, Chris over 10 years ago

I would rather we have something a bit more formal than diffs. I need to think about it.

#3

Updated by Rogers, Chris over 10 years ago

  • Priority changed from Normal to High
#4

Updated by Rogers, Chris over 10 years ago

How strict do we want to be about python style? I wrote an automatic style checker, in fact to help Matt L with his code (simple wrapper to pylint). Comes up with a whole bunch of errors, many in my code.

I notice we had pychecker in 40python_extras.bash, but it's commented out. Any reason? Also, is there any preference for pychecker over pylint?

#5

Updated by Tunnell, Christopher over 10 years ago

who knows why I took it out. I think it had build problems on some system.

I'd say toss in pylint then we can use:

  1. pylint: disable msg: C2342

where applicable. We can have people work on that at the pre-CM session. :)

#6

Updated by Rogers, Chris over 10 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Added in r568

#7

Updated by Rogers, Chris over 10 years ago

  • Target version changed from Future MAUS release to MAUS-v0.0.3

Also available in: Atom PDF