On Monday 26 April 2010 14:57:34 Sylvain Thénault wrote: > > For bw compatibiliy, would it be possible to say that "Doubtful" is > > considered as a Warning sub category, and D0105 and W0105 would both > > be ok? > > I'm really not keen on a 'doubtful' category... We should fix those > that are definitly not in the right category, and keep other as they > are (for instance, __future__ not first statement is an Error).
Maybe I can make myself more clear with a typical use case: suppose you start on a project with 100 000 lines and tousands of commits with many developpers from different companies, some of them using OS from extra-UNIX galaxy or never heard about PEP8. In that case, I can not quick fix most of the warnings listed under c/ because I don't know the project. Basically, everything listed under c/ needs some thinking where as I can fix a/ and b/ without (hence possible in a pre-commit situation or on the fly). So imo, the c/ warnings are 'bad smell' (Warning), but in same time Refactoring issues. I don't think, you want to move all or most of them to the Refactoring (and moving maybe most of a/ to Error). But if you do, won't it break bw compability either ? -- Emile Anclin <emile.anc...@logilab.fr> http://www.logilab.fr/ http://www.logilab.org/ Informatique scientifique & et gestion de connaissances _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
