disable=all from a pylintrc file?
I'm trying to whitelist checkers from a pylintrc file for pylint, but when I have: [MESSAGES CONTROL] disable=all enable=old-style-class nothing is outputted. When I comment out the `disable` line then everything is outputted. And if I set `disable` to something like `no-init` then that works, so I know the pylintrc file is working properly. How can I get the equivalent of --disable=all specified in a pylintrc file so I can select exactly what checkers I want to run?
On 09 juin 19:52, Brett Cannon wrote:
I'm trying to whitelist checkers from a pylintrc file for pylint, but when I have:
[MESSAGES CONTROL] disable=all enable=old-style-class
nothing is outputted. When I comment out the `disable` line then everything is outputted. And if I set `disable` to something like `no-init` then that works, so I know the pylintrc file is working properly.
How can I get the equivalent of --disable=all specified in a pylintrc file so I can select exactly what checkers I want to run?
This is probably due to the following bug in logilab-common https://www.logilab.org/ticket/185648 hopefuly it's targeted for 0.62 which should be released soon. -- Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org
On Tue Jun 10 2014 at 4:17:38 AM, Sylvain Thénault < sylvain.thenault@logilab.fr> wrote:
I'm trying to whitelist checkers from a pylintrc file for pylint, but when I have:
[MESSAGES CONTROL] disable=all enable=old-style-class
nothing is outputted. When I comment out the `disable` line then everything is outputted. And if I set `disable` to something like `no-init` then
On 09 juin 19:52, Brett Cannon wrote: that
works, so I know the pylintrc file is working properly.
How can I get the equivalent of --disable=all specified in a pylintrc file so I can select exactly what checkers I want to run?
This is probably due to the following bug in logilab-common https://www.logilab.org/ticket/185648
hopefuly it's targeted for 0.62 which should be released soon.
Great! Then I will continue to move forward with my pylint explorations with the assumption that this will work at some point.
participants (2)
-
Brett Cannon
-
Sylvain Thénault