pyflakes

We use Hudson for continuous integration with the Violations Plugin which parses our output from pylint. However, pylint is a bit too strict, and hard to configure. What we'd rather use is pyflakes which would give us the right level of "You're doing it wrong." You can adapt pyflakes and pep8 output to work with the Violations pylint plugin. pyflakes path/to/src | awk -F\: '{printf "%s:%s: [E]%s\n", $1, $2, $3}' > violations.pyflakes.txt pep8 path/to/src | awk -F\: '{printf "%s:%s: [%s]%s\n", $1, $2, substr($4,2,4), substr($4,6)}' > violations.pep8.txt You could use a regex or concatenate the

I want to use pep8 as my makeprg in order to check and fix my code compliance to PEP8 (Style guide for python code) . I used the command :set makeprg=pep8\ --repeat\ % , and when I do :make it works, the error list is populated and I can use :cn , :cp and :copen to navigate and see the error list in the QuickFix window. But as soon as I change something in my python source file the errorlist becomes empty, the QuickFix window loses its content and I cannot navigate the list anymore. I suspect that this is caused by PyFlakes, a Vim extension that highlights Python errors on-the-fly. How can I

I am currently using the following code to hook up flymake and Pyflakes in emacs: (defun flymake-create-temp-in-system-tempdir (filename prefix) (make-temp-file (or prefix "flymake"))) and then I pass this function to flymake-init-create-temp-buffer-copy . (Taken from http://hustoknow.blogspot.com/2010/09/emacs-and-pyflakes-using-tmp-directory.html ). This code worked fine until yesterday. When I visit certain Python files, I get the following error: switched OFF Flymake mode for buffer admin.py due to fatal status CFGERR, warning Configuration error has occured while running (pyflakes ../../.

I'm trying to use flymake to run pyflakes, as suggested here This works fine for local files, and almost works with remote files with a bit of tweaking, but I'm left with a problem where flymake/pyflakes 'modifies' the buffer when it runs (although nothing actually seems to change), which renders it a bit useless in practice (e.g. saving a file runs flymake which immediately modifies the buffer again). Here's what I did to almost get it working: Installed pyflakes on the remote box. Customized my tramp-remote-process-environment variable so that pyflakes could be found in its PATH Used a