Skip to main content

A More Complete PyLint on Windows Walkthrough

Others have posted about getting pylint installed on Windows, but I always fell short getting the steps to lead to the destination. Some tinkering and I got it right. This also includes the instructions to get it integrated into Komodo.
  1. Grabbing the Goods
    First off the bat we need to grab all the packages we need. pylint depends on two other packages from Logilabs, who write pylint for us. We need to grab the latest releases of pylint, logilab-astng, and logilab-common.
  2. Extract all of these somewhere to install from.
  3. Open a command shell and move to each of the directories, executing the install command in each:
    python setup.py install
  4. Feel free to remove the extracted files now that everything has been installed. You can use pylint now. On to Komodo integration.
  5. In Komodo, open the toolbox from the View menu with View->Tabs->Toolbox. Now, click your "Add Item to Toolbox" button in the new tab, and select "New Command..." to add a command to Komodo that will analyze your current file with pylint.
  6. For the command enter the line 'python -c "import sys,pylint.lint;pylint.lint.Run(sys.argv[1:])" "%F"'. This will import pylint, handle spaces in Windows filenames, and run the processing on your file.
  7. Check the "Parse output with:" box and enter this regular expression to parse the lines from pylint, '.*?:(?P<line>\d+):\s*(?P<content>.*?)$'. Also, check the "Show parsed output as list" box.
  8. Optionally, bind a key shortcut from the Key Binding tab. I use ctrl+alt+L.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…

Using a React Context as a Dispatch Replacement

React Contexts are the pretty little bows of the React world.

Here's a really quick example of the kind of messy code you can cleanup by using contexts, without dragging in a larger dependency like Redux or even Flux. Starting backwards with a diff showing lines of code I was able to remove:


All the properties I was able to remove were just pass-through. The Carousel component didn't care about any of them, but it had to pass through these callbacks so the multiple TaskList components inside the carousel could invoke actions. They were removed from the Component class itself, too, since it no longer needed to pass them through.

Where did they all go?


My ActionContext removed all the need for these passthroughs by providing a single simple helper method, action(), that components rendered under it can access.


I really enjoy the pattern of passing a single callback through a context and removing what used to be lots of callback properties. Of course, I could be using a proper di…