Hi there, we (Logilab) have been recently working on pylint for a customer, and provided at this occasion a couple of pull requests. I would like your opinion about some of them, not really technically but rather if you think the functionnality should go in pylint or not.
The first one is about a message for 'else: if <cond>' that could be turned into 'elif <cond>: https://bitbucket.org/logilab/pylint/pull-requests/300/check-for-use-of-else-if-i The other one is about a message about avoiding unnecessary usage of 'not' identifier. This is explained in https://bitbucket.org/logilab/pylint/issues/670/warning-upon-unneeded-negations and there is a discussion about whether we should add a special case for class implementin '__neq__'. See https://bitbucket.org/logilab/pylint/pull-requests/293/check-for-nots-too-many-in-comparison/activity# You might also be interested about this one : https://bitbucket.org/logilab/pylint/pull-requests/299/check-if-the-type-of-a-variable-is/diff which checks for assigment of several types to a single identifier. Depending on the community (you) opinion, I'll integrate those in pylint or in a separated checker we've done for our customer. Regards -- 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 _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
