On Monday 26 April 2010 12:21:50 Sylvain Thénault wrote: > > 2/ Imho, we should add "--list-msgs" to "pylint --help" : we often > > want to disable quickly a message and might not remember the id, or > > would like to have a fast overview. > > > I prefer using a run with --include-ids in such case. Maybe that should > be on by default. > I am alright with --include-ids by default (since it's even in a pylint alias for me ;) and I also disable --report by default).
But if we don't do that, imho, re-run pylint with the '--include-ids' option is not the right solution for searching a mesage id, when you run pylint on a big project, with a undesired warning somewhere. (As a pylint beginner I might not even know about the ids) If we have simple --enable / --disable options, we should give quick access to the list of possible messages without having to search in --long-help for the --list-msgs option to finally find the id of the message. > > 3/ I also would like > > -w, --warning meaning --disable=C,R > > or better : > > -q, --quick meaning disable=C,R and disable some more > > warnings which we don't care in pre-commit like situation (for > > example the list of messages under c/ listed below) > > > If we go that way, I would prefer adding a notion of 'mode', > corresponding to a specific configuration. We akready have an 'error' > mode. You propose a 'warning' mode. I've greatly simplified the command > line, let's avoid recomplixie it by adding more and more options for > every mode people can see. We should have -m/--mode > [error|warning|...]. Ideally people can define their own modes. > > > > Completed list of different kind of messages (proposal) > > what are you proposing exactly? > I want to have a pylint "quick" as a pre-commit tool. I would be fine with introducing a 'quick' mode. So what I propose, is that $ pylint --mode quick would not take those messages listed under c/ because they can not be fixed quickly and are not necessarily errors. > I'm not sure I want to create more categories than we already have. > Some messages could actually be moved to a better suited category, but > that should be done when it's really desirable, since it's a bw > incompatible change that may be painful to users (update of > configuration file and inline message control...) For now, we have 55 W 46 E 15 R 13 C 8 F so, this "might" be a hint to the fact, that the "Warning" category is getting quite big, maybe too big. But, indeed I am not sure, I just want a quick mode. 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? -- 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
