Sorry this took so long to get through moderation Patrick. In the
future, if you're on the list you can post to it.
On Sun, Dec 22, 2013 at 11:22 PM, Patrick Jakubowski
Hi all,
I'm upgrading from pylint 0.27.0 to 1.0.0 in my company's code base and I've run into a bit of an issue. For several of our modules, we use 'pylint: disable=C0302', to disable the too-many-lines error for the module. In pylint 0.26 this worked just fine as long as we put the line somewhere at the top of the module before any imports, like so:
#! /usr/bin/env python # pylint: disable=C0302 <rest of code>
However, after upgrading to 1.0.0 it seems that the disable comment for C0302 HAS to go on the first line. This gets awkward because one has to mix it with the shebang line, like so:
#! /usr/bin/env python # pylint: disable=C0302 <rest of code>
I have a feeling that this will be difficult and awkward for other developers in our code base to figure out. It's also very strange because module-wide suppression of other errors (e.g. W0223) continue to work even if they are not on the very first line. Is this a bug or is there some other way to accomplish a module-wide suppression of C0302 without mixing it with the shebang?
Thanks, Patrick Jakubowski _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality