On 27 avril 11:17, Emile Anclin wrote: > 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 ?
That's why I say: - a new category won't solve that, this is your idea about it, other people will have another one -> you need a custom configuration file. If it can be referenced through --mode, it's even nicer. - moving message from a category to another breaks compatibility, let's only omove those which really belong to another one. -- 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
