Re: Emacs 23, Python, epylint, pylint

[Richard Riley]

Richard Riley <rileyrgdev@gmail.com> writes:

> I have followed the advice here:
>
> http://stackoverflow.com/questions/1259873/how-can-i-use-emacs-flymake-mode-for-python-with-pyflakes-and-pylint-checking-cod
>
> or
>
> http://tinyurl.com/yfshb5b
>
> And successfully have pylint and emacs highlighting errors in my .py
> files courtesy of flymake. The problem is that I can't see anywhere the
> actually error description. Can anyone help please?
>
> The epylint script I have is this:
>
> ,----
> | #!/usr/bin/env python
> | 
> | import re
> | import sys
> | 
> | from subprocess import *
> | 
> | p = Popen(
> |     "pylint -f parseable -r n %s"%
> |     sys.argv[1], shell = True, stdout = PIPE).stdout
> | 
> | for line in p:
> |     match = re.search("\\[([WECR])(, (.+?))?\\]", line)
> |     if match:
> |         kind = match.group(1)
> |         func = match.group(3)
> | 
> |         if kind in ["W","C","R"]:
> |            msg = "Warning"
> |         else:
> |            msg = "Error"
> | 
> |         if func:
> |             line = re.sub("\\[([WECR])(, (.+?))?\\]",
> |                           "%s (%s):" % (msg, func), line)
> |         else:
> |             line = re.sub("\\[([WECR])?\\]", "%s:" % msg, line)
> |     print line,
> | 
> | p.close()
> `----
>

OK, its done so that you need to (yuck!) hover your mouse over the
hilited error. Kind of in the face of keyboard driven emacs, but at
least one can see the error. If anyone has a patch/fix/advice on how to
change this to show the errors in a buffer and maybe next error/previous
error then that would be great. In fact pylint.el does something like
that but it would be nice in conjunction with the flymake dynamic code
checking and error hiliting.