Mailman 3 December 2013 - code-quality

pylint: disable for too-many-lines must go on first line of module?
by Patrick Jakubowski 06 Jan '14

06 Jan '14

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

3 2

pyflakes development dead again?
by Laurent Bachelier 11 Dec '13

11 Dec '13

It's been 5 months since the last commit on https://github.com/pyflakes/pyflakes and the critical bugs are starting to pile up.

1 0

Compatibility question
by Ron Burnett 02 Dec '13

02 Dec '13

Sir/Madam I am interested in determining whether asteroid 1.0.1 can be installed via the command: python setup.py install when you are using python 2.4? Regards Ron Ron Burnett Staff Test Engineer [cid:image001.png@01CE9342.6D040E30] Links House, 15 Links Place, Edinburgh, UK, EH6 7EZ T: + 44-131-561-4852 Ron.Burnett(a)SanDisk.com ________________________________ PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies).

2 1