{"id":315,"date":"2011-08-25T00:53:41","date_gmt":"2011-08-24T21:53:41","guid":{"rendered":"http:\/\/www.held.org.il\/blog\/?p=315"},"modified":"2011-08-25T00:53:41","modified_gmt":"2011-08-24T21:53:41","slug":"pylint-vim-plugin-update-0-24-0-support","status":"publish","type":"post","link":"http:\/\/www.held.org.il\/blog\/2011\/08\/pylint-vim-plugin-update-0-24-0-support\/","title":{"rendered":"pylint Vim plugin update (0.24.0 support)"},"content":{"rendered":"<p><strong>[Executives' summary <\/strong>(in case any executive uses Vim)<strong> - get <a href=\"https:\/\/github.com\/orenhe\/pylint.vim\">this updated pylint.vim<\/a> for compatibility with pylint 0.24.0 changes]\u00c2\u00a0<\/strong><\/p>\n<p>Integrating <a href=\"http:\/\/pypi.python.org\/pypi\/pylint\">Python code checker<\/a> into <a href=\"http:\/\/www.vim.org\">Vim<\/a> is really cool. It lets Vim provide (relatively) quick feedback on your code, be it a conventions warning or syntax error. That, in my opinion, increases coding productivity slightly.<\/p>\n<p>The problem is, that configuring the vim-pylint integration is hell. for two reasons mainly:<\/p>\n<ol>\n<li>Doing it manually requires understanding of the unpleasant errorformat syntax and some other vim tricks.<\/li>\n<li>No good zero-setup plugin is available: <a href=\"http:\/\/www.vim.org\/scripts\/script.php?script_id=891\">official pylint.vim<\/a> is unmaintained. I used to use <a href=\"code.google.com\/p\/vim-python-ide\/\">this fork<\/a>, but its not really active anymore.<\/li>\n<\/ol>\n<p>Specifically, since I upgraded to latest pylint (0.24.0),\u00c2\u00a0 Vim stopped showing pylint's hints. That's because pylint's output was modified to contain the column number as well.<\/p>\n<p>I've <a href=\"https:\/\/github.com\/orenhe\/pylint.vim\">re-forked it<\/a>, and updated it to support pylint 0.24.0. Note that it will probably fail with older versions. Please try it and <a href=\"https:\/\/github.com\/orenhe\/pylint.vim\/issues\">send feedback<\/a> (you can comment this post if easier).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[Executives&#8217; summary (in case any executive uses Vim) &#8211; get this updated pylint.vim for compatibility with pylint 0.24.0 changes]\u00c2\u00a0 Integrating Python code checker into Vim is really cool. It lets Vim provide (relatively) quick feedback on your code, be it a conventions warning or syntax error. That, in my opinion, increases coding productivity slightly. The [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[198,164,93,124],"_links":{"self":[{"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/posts\/315"}],"collection":[{"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/comments?post=315"}],"version-history":[{"count":0,"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/posts\/315\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/media?parent=315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/categories?post=315"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.held.org.il\/blog\/wp-json\/wp\/v2\/tags?post=315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}