Hi Ian,

I'm actually on the mailing list as well (since maybe 2 weeks ago). You might remember my email about proposing a common format for error messages. I think it's a great idea to coordinate development of our static-analysis tools. Adding pep257 to flake8 might be a good idea. Shall we call it fla257ke8? :o)

But I'm not sure I understand the purpose of flake8. Wouldn't having a common error format between all the tools defeat the purpose of flake8? Then a dummy runner would suffice. Imagine a world where all static analysis tools have a common output format and same command-line interface and error conventions.

Cheers,

Vladimir

15.04.2013, 20:24, "Ian Cordasco" <graffatcolmingov@gmail.com>:

Hey,

I'm a maintainer of flake8* and we just received a feature request[1]
to integrate pep257 with the tool. I was hoping to start a discussion
on the code-quality mailing list[2] about whether to include it in the
core of the tool or as a plugin. It would be fantastic if you and the
other maintainers/authors of the pep257 tool could join us in the
discussion. Tarek Ziade (flake8's original author) and Florent Xicluna
(pep8's maintainer and my co-maintainer on flake8) are all part of the
list as well as a portion of python-dev, and testing-in-python. The
list (we hope) will generate some new ideas and discussion about how
to measure and ensure quality in python code and as far as I'm
concerned pep257 is a part of that (I just have had the misfortune of
only finding out about it today).

Thanks,
Ian

* flake8 is a glue project that uses mccabe, pep8 and pyflakes to help
python programmers write cleaner code

[1] https://bitbucket.org/tarek/flake8/issue/101/support-pep257
[2] http://mail.python.org/mailman/listinfo/code-quality