The must-have features of pyflakes-vim have been merged into Syntastic, which has a plugin-based syntax checking backend. This means you can check many different languages on the fly. I recommend using Syntastic unless you're mostly just editing Python.
A Vim plugin for checking Python code on the fly.
PyFlakes catches common Python errors like mistyping a variable name or accessing a local before it is bound, and also gives warnings for things like unused imports.
pyflakes-vim uses the output from PyFlakes to highlight errors in your code. To locate errors quickly, use quickfix commands like :cc.
Make sure to check vim.org for the latest updates.
Make sure your
.vimrchas:filetype on " enables filetype detection filetype plugin on " enables filetype specific plugins- Download the latest release.
If you're using pathogen, unzip the contents of
pyflakes-vim.zipinto its own bundle directory, i.e. into~/.vim/bundle/pyflakes-vim/.Otherwise unzip
pyflakes.vimand thepyflakesdirectory into~/.vim/ftplugin/python(or somewhere similar on your runtime path that will be sourced for Python files).
If you're running pyflakes-vim "from source," you'll need the PyFlakes library on your PYTHONPATH somewhere. (It is included in the vim.org zipfile.) I recommend getting the github.com/pyflakes PyFlakes fork, which retains column number information, giving more specific error locations.
git clone --recursive git://github.com/kevinw/pyflakes-vim.gitor use the PyFlakes submodule:
git clone git://github.com/kevinw/pyflakes-vim.git
cd pyflakes-vim
git submodule init
git submodule updateSet this option in your vimrc file to disable quickfix support:
let g:pyflakes_use_quickfix = 0The value is set to 1 by default.
- signs support (show warning and error icons to left of the buffer area)
- configuration variables
- parse or intercept useful output from the warnings module
Please see http://www.vim.org/scripts/script.php?script_id=2441 for a history of all changes.