On 17 février 01:38, Fletcher Johnson wrote: Hi, > I'm looking into fixing this bug, but I don't have a very good > understanding of where I should start tackling this bug. Can any > body recommend a file or a set of files in the source where I should > concentrate my efforts?
that's rather a new feature than a bug ;) This is a new check that could be added for instance to the 'base' checker (eg pylint/checkers/base.py). Basically, you should: * add a visit_raise method that will check the nature of the raised expression to detect potential misusage of a 2-uple * add test for this by adding a python file to pylint/test/input and expected message to pylint/test/message * check everything is fine by running "python func_test.py" in the test directory * provides a patch :) Don't hesitate to ask the list for more questions -- Sylvain Thénault LOGILAB, Paris (France) 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 _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
