On 19 janvier 18:12, Kay Hayen wrote: > Hello, Hi, > Error numbers in tools such as pep8 and pyflakes (although flake8 adds > > them to pyflakes) are usually not made to be entirely successive. For > > the most part, there are groupings of errors. The best explanation of > > this is pep8's documentation: > > http://pep8.readthedocs.org/en/latest/intro.html#error-codes > > > > Anything starting with E1 is related to indentation, anything starting > > with E2 is related to whitespace. These are conceptually classes of > > errors. PyLint also follows this convention if I remember correctly > > and you would do well to do the same. The error codes that Flake8 adds > > to PyFlakes follow that convention as well. > > > > So for my compiler Nuitka, there are very few warnings so far, mostly > because > it is very limited in its tracing abilities, but I am expanding this now, > and so far > I was kind of clueless on how to properly format error and warning messages. > > It probably will a while, before I find the need to expand it, but it would > be good > to have a common ground, reusable data. For PyLint, these texts seem spread > out in the variables files. > > Is there an easy way to access the PyLint warning/error message texts. Would > you be OK with me to grep these out of PyLint or Wiki, and use them under > ASF2 > in my project as well. I would of course prefer, for these to exist a place > that makes > reuse easier. > > Basically, I am saying, why isn't this some kind of standard. And can we > make it > one.
as Pylint author I would say it's fine by me but warn that in Pylint we're slowly but surely moving from numercial ids (E0601, W0402...) to symbolic ids (bad-indent, bad-name) which carry slightly less information but are much more easy to read and remember. -- Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42) 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 _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
