Support pylama for python

[kevinoid]

pylama is a popular (>500 stars) plugin-based code audit tool for Python which includes plugins for several other popular tools.

The pylama ALE linter is based on existing python linters and attempts to adopt the same conventions and code as much as possible.

Thanks for considering,
Kevin

[RyanSquared]

Just to clarify, a "Traceback" message is a possible flaw in the linter itself and not something like a syntax error?

[kevinoid]

Just to clarify, a "Traceback" message is a possible flaw in the linter itself and not something like a syntax error?

A traceback is printed whenever a linter plugin encounters an unhandled exception. (See pylama/core.py:85-87) The unhandled exception could be due to an unexpected internal error or a syntax error severe enough that the linter plugin can't analyze the file.

For example, the pydocstyle plugin throws ParseError when from __future__ import with_statement occurs after a non-__future__ import, which is what I used to generate the traceback test case.

Does that answer your question?

[RyanSquared]

If this is a common case, I think there should be a better way to solve it than hide the message behind :ALEDetail, such as putting only the repr-like format of the error as the message, then mentioning :ALEDetail.

[kevinoid]

I expect it to be about as frequent as python/flake8 and python/vulture, which both share the same behavior for tracebacks. Perhaps traceback detection and handling should be shared between all of them?

[kevinoid]

I updated the pull request with an additional commit that consolidates the traceback parsing between the Python linters and uses the exception line (with the type and message) as the ALE text. Let me know what you think.

[w0rp]

Cheers! 🍻

[kevinoid]

Thanks @w0rp! 🥂