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

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …