1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
============================
Editor and IDE integration
============================
To use Pylint with:
- Emacs_, see http://www.emacswiki.org/emacs/PythonProgrammingInEmacs#toc8,
- Vim_, see http://www.vim.org/scripts/script.php?script_id=891,
- Eclipse_ and PyDev_, see http://pydev.org/manual_adv_pylint.html,
- Komodo_, see http://mateusz.loskot.net/posts/2006/01/15/running-pylint-from-komodo/,
- gedit_, see https://launchpad.net/gedit-pylint-2 or https://wiki.gnome.org/Apps/Gedit/PylintPlugin,
- WingIDE_, see http://www.wingware.com/doc/edit/pylint,
- PyCharm_, see http://blog.saturnlaboratories.co.za/archive/2012/09/10/running-pylint-pycharm.
- TextMate_,
Pylint is integrated in:
- Eric_ IDE, see the `Project > Check` menu,
- Spyder_, see http://packages.python.org/spyder/pylint.html,
- pyscripter_, see the `Tool -> Tools` menu.
.. _Emacs: http://www.gnu.org/software/emacs/
.. _Vim: http://www.vim.org/
.. _Eclipse: https://www.eclipse.org/
.. _Eric: http://eric-ide.python-projects.org/
.. _pyscripter: http://code.google.com/p/pyscripter/
.. _pydev: http://pydev.org
.. _Komodo: http://www.activestate.com/Products/Komodo/
.. _gedit: https://wiki.gnome.org/Apps/Gedit
.. _WingIDE: http://www.wingware.com/
.. _spyder: http://code.google.com/p/spyderlib/
.. _PyCharm: http://www.jetbrains.com/pycharm/
.. _TextMate: http://macromates.com
Using Pylint thru flymake in Emacs
==================================
To enable flymake for Python, insert the following into your .emacs:
.. sourcecode:: common-lisp
;; Configure flymake for Python
(when (load "flymake" t)
(defun flymake-pylint-init ()
(let* ((temp-file (flymake-init-create-temp-buffer-copy
'flymake-create-temp-inplace))
(local-file (file-relative-name
temp-file
(file-name-directory buffer-file-name))))
(list "epylint" (list local-file))))
(add-to-list 'flymake-allowed-file-name-masks
'("\\.py\\'" flymake-pylint-init)))
;; Set as a minor mode for Python
(add-hook 'python-mode-hook '(lambda () (flymake-mode)))
Above stuff is in ``pylint/elisp/pylint-flymake.el``, which should be automatically
installed on Debian systems, in which cases you don't have to put it in your ``.emacs`` file.
Other things you may find useful to set:
.. sourcecode:: common-lisp
;; Configure to wait a bit longer after edits before starting
(setq-default flymake-no-changes-timeout '3)
;; Keymaps to navigate to the errors
(add-hook 'python-mode-hook '(lambda () (define-key python-mode-map "\C-cn" 'flymake-goto-next-error)))
(add-hook 'python-mode-hook '(lambda () (define-key python-mode-map "\C-cp" 'flymake-goto-prev-error)))
Finally, by default flymake only displays the extra information about the error when you
hover the mouse over the highlighted line. The following will use the minibuffer to display
messages when you the cursor is on the line.
.. sourcecode:: common-lisp
;; To avoid having to mouse hover for the error message, these functions make flymake error messages
;; appear in the minibuffer
(defun show-fly-err-at-point ()
"If the cursor is sitting on a flymake error, display the message in the minibuffer"
(require 'cl)
(interactive)
(let ((line-no (line-number-at-pos)))
(dolist (elem flymake-err-info)
(if (eq (car elem) line-no)
(let ((err (car (second elem))))
(message "%s" (flymake-ler-text err)))))))
(add-hook 'post-command-hook 'show-fly-err-at-point)
Alternative, if you only wish to pollute the minibuffer after an explicit flymake-goto-* then use
the following instead of a post-command-hook
.. sourcecode:: common-lisp
(defadvice flymake-goto-next-error (after display-message activate compile)
"Display the error in the mini-buffer rather than having to mouse over it"
(show-fly-err-at-point))
(defadvice flymake-goto-prev-error (after display-message activate compile)
"Display the error in the mini-buffer rather than having to mouse over it"
(show-fly-err-at-point))
Setup the MS Visual Studio .NET 2003 editor to call Pylint
==========================================================
.. image:: _static/vs2003_config.jpeg
The output of Pylint is then shown in the "Output" pane of the editor.
.. _pylint_in_textmate:
Integrate Pylint with TextMate
==============================
Install Pylint in the usual way::
pip install pylint
Install the `Python bundle for TextMate <https://github.com/textmate/python.tmbundle>`_:
#. select *TextMate* > *Preferences*
#. select the *Bundles* tab
#. find and tick the *Python* bundle in the list
You should now see it in *Bundles* > *Python*.
In *Preferences*, select the *Variables* tab. If a ``TM_PYCHECKER`` variable is not already listed, add
it, with the value ``pylint``.
The default keyboard shortcut to run the syntax checker is *Control-Shift-V* - open a ``.py`` file
in Textmate, and try it.
You should see the output in a new window:
PyCheckMate 1.2 – Pylint 1.4.4
No config file found, using default configuration
Then all is well, and most likely Pylint will have expressed some opinions about your Python code
(or will exit with ``0`` if your code already conforms to its expectations).
If you receive a message:
Please install PyChecker, PyFlakes, Pylint, PEP 8 or flake8 for more extensive code checking.
That means that Pylint wasn't found, which is likely an issue with command paths - TextMate needs
be looking for Pylint on the right paths.
Check where Pylint has been installed, using ``which``::
$ which pylint
/usr/local/bin/pylint
The output will tell you where Pylint can be found; in this case, in ``/usr/local/bin``.
#. select *TextMate* > *Preferences*
#. select the *Variables* tab
#. find and check that a ``PATH`` variable exists, and that it contains the appropriate path (if
the path to Pylint were ``/usr/local/bin/pylint`` as above, then the variable would need to
contain ``/usr/local/bin``). An actual example in this case might be
``$PATH:/opt/local/bin:/usr/local/bin:/usr/texbin``, which includes other paths.
... and try running Pylint again.
|
