| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
These were introduced in 3.6 so they're not an option. Otherwise they'd
be a good idea.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
We have been stuck on pylint <2 for a long time now because it dropped
some of the python 2 lints we rely on. We maintain compatibility with
python 2.6+ and 3.5+ and a lack of lints makes especially the former
much harder. Incompatibilities had already snuck in in the form of
implicit format specs. By implementing a custom checker we can make sure
this doesn't happen again.
|
| |
|
|
|
|
|
|
|
|
| |
`no-else-break/continue/raise/return` because they're nonsense and
result in actively less readable code.
`useless-object-inheritance` because that's a py3-ism.
`import-outside-toplevel` because we use this in many places to good
effect.
|
| |
|
|
|
| |
I'm not sure if the suggested solution is portable between Python 2
and 3, so I'm disabling it for now.
|
| | |
|
| | |
|
| |
|