On 15 mars 08:27, Colin Morris wrote: > Hi, > > > > Pylint has a lot of options to controlling the behaviour and output. > > > But it is my experience that there are so many that they are very > > > hard to find and use correctly. > > > > do you have some ideas about how to improve this? Do you see some > > options which are in your opinion useless? > > While I wasn't the target of this question, I wouldn't mind weighing in on > this, as it's something I was just speaking with one of my peers about.
feel free, questions on mailing-list are almost never limited to the original poster. > Obviously, there are some options that you might reasonably want to tweak > across different runs of pylint without having to edit the rc file > (--output-format, or --profile for example). There are some things that > simply *must* be command line arguments, like --rc-file, or --help, or > --generate-man. But aside from those, there are a lot of options that you > would probably want to just set and forget. For example, I can't imagine > anyone wanting to torture themselves with typing in a bunch of > regular-expressions that their variable names should match for every time > they run pylint. [snip] that's right, and imo what you're describing is that we want much shorter --help, with maybe a --long-help providing full options description. Also I think we should hide --profile and --generate-man options which only target pylint developpers. I agree that's also definitly in the top of the wish list to improve first pylint experience. -- 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
