Hey all, I would first like to apologize for my complete disappearance from everything related to this list. Between finishing my masters, moving 1000 miles away and starting a new job (before I was even able to acquire domestic internet), I haven't had time for much of anything. In spite of that poor excuse, I'm sprinting on Flake8 today (trying to fix bugs and get other things written), and I wanted community feedback on a few things. First, is there any interest in developing a pylint plugin for Flake8? If so, who's interested in working with me on it. (I doubt we will finish it today, but I'd at least like to start it.) Second, can anyone provide some guidance (or at least opinions) on issue #85 on Flake8's bug tracker[1]. I'm conflicted about using a script to manage which version of python we use and I am quite partial to the method of appending the python version to the executable's name. However, if others have strong opinions on this, I'm quite willing to listen and would love more information. Finally, if there is anyone willing to collaborate with me on issues #95 [2], #97 [3], and #99 [4], I'd heartily appreciate it. To save you a few clicks, here are some summaries of those issues: #95: Generate code quality visualizations akin to: https://github.com/jsoverson/plato #97: Maintainability index based off McCabe, Halstead and SLOC #99: Machine readable output. This can probably take full advantage of pep8 features without needing to do anything special with Flake8. Firehose may also be of interest. [1]: https://bitbucket.org/tarek/flake8/issue/85 [2]: https://bitbucket.org/tarek/flake8/issue/95 [3]: https://bitbucket.org/tarek/flake8/issue/97 [4]: https://bitbucket.org/tarek/flake8/issue/99 Thanks in advance, Ian