A suggestion is to use the compiler functionality in Vim (see :help :compiler). To create a compiler file for pychecker, create the following in 'pychecker.vim' (and place it in e.g. "~/.vim/compiler/" on a unix-style system)::

One flaw with the compiler way is that it searches all modules recursively for errors by default. It then opens the current window to the first error it finds, commonly in a module. While this is good if you wrote and are testing the modules, its not so good when you did not and would rather focus on your own project.

I tried to fix this by editting the makeprg line to match that used above. However, the compiler method tends to break on simple errors. For example:

Then I made one small change to a file that previously tested errorfree. I changed a "not" to a "!" in an if statement (common mistake for me).

I then entered the :make command and Vim responded with:

"pydsh" [New File]
(4 of 4): NOT PROCESSED UNABLE TO IMPORT
Hit ENTER or type command to continue
and opened a new empty buffer (:bd to close).

On the other hand, I pressed F3 or F4 for my function and was presented with a open cwindow below my window with one line in it: "pydsh.py|860| [E] invalid syntax" which when selected took me to the line with the problem.