On 12 mars 21:57, Colin Morris wrote: > I quite like these suggestions, especially number 1. A few notes: > > > Proposed output for messages: > > > +-----------+------------+---- > > ---------+ > > |message id |occurrences |reference | > > +===========+============+=============+ > > +-----------+------------+-------------+ > > |E0602 |2 |PEP 333 | > > +-----------+------------+-------------+ > > |W0612 |1 |http:// | > > +-----------+------------+-------------+ > > |W0301 |1 |file:///....-+ > > +-----------+------------+-------------+ > > |F0401 |1 |(field empty)| > > +-----------+------------+-------------+ > > > > where the links might be to the pylint error code wiki, python peps, > > pylint documentation, or local documentation. > > Would this be for html output mode? I like the idea, but I can't > imagine someone wanting to transcribe the URLs into their browser from > the text output.
but I don't think a lot of people are using the html output. > > It may be possible to generate a useful English description of the problem > > by looking at the expression and how it fails to match the name. For > > example, whether it encounters an invalid character (if so, indicate which > > one), whether it has an issue with the length of the name etc. Maybe a nice > > challenge for a student? > > A simpler implementation might just be to associate a string with each > regex that gets printed with the accompanying message (e.g. "Function > names should be in pothole_case", "Class names should be in > CapWords"). If someone wants to define their own regexes, they could > also optionally include a string briefly describing the rule or > rationale behind each. imo this complexify the (already too complex) configuration and I'm not sure that's worth it. > > It could be a Wiki where experienced users can add the motivation behind the > > checks pylint does. Adding text to a Wiki has a lower barrier of entry than > > submitting a patch. > > Conveniently enough, such a thing exists already! > http://pylint-messages.wikidot.com/ yes, and that's a great initiative. We should at least prevent people hosting it if pylint starts to provides direct link to this site. But as I said I think we should discuss more about this enhancement. -- 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
