There are several code analysis tools for Python. The most well known is pylint. Then there's pychecker and now we're moving on to pyflakes. The pyflakes project is a part of something known as the Divmod Project. Pyflakes doesn't actually execute the code it checks, unlike pychecker. Of course, pylint also doesn't execute the code. Regardless, we'll take a quick look at it and see how pyflakes works and if it's better than the competition.
As you have probably guessed, pyflakes is not a part of the Python distribution. You will need to download it from PyPI or from the project's launchpad page. Once you have it installed, you can run it against some of your own code. Or you can follow along and see how it works with our test script.
We'll be using a super simple and pretty silly example script. In fact, it's the same one we used for the pylint and pychecker articles. Here it is again for your viewing pleasure:
import sys
########################################################################
class CarClass:
""""""
#----------------------------------------------------------------------
def __init__(self, color, make, model, year):
"""Constructor"""
self.color = color
self.make = make
self.model = model
self.year = year
if "Windows" in platform.platform():
print "You're using Windows!"
self.weight = self.getWeight(1, 2, 3)
#----------------------------------------------------------------------
def getWeight(this):
""""""
return "2000 lbs"
As was noted in the other articles, this dumb code has 4 issues, 3 of which would stop the programming from running. Let's see what pyflakes can find! Try running the following command and you'll see the following output:
C:\Users\mdriscoll\Desktop>pyflakes crummy_code.py
crummy_code.py:1: 'sys' imported but unused
crummy_code.py:15: undefined name 'platform'
While pyflakes was super fast at returning this output, it didn't find all the errors. The getWeight method call is passing too many arguments and getWeight method itself is defined incorrectly as it doesn't have a "self" argument. Well, you can actually call the first argument anything you want, but by convention it's usually called "self". If you fixed your code according to what pyflakes told you, your code still wouldn't work.
The pyflakes website claims that pyflakes is faster than pychecker and pylint. I didn't test this, but anyone who wants to can do so pretty easily by just running it against some big files. Maybe grab the BeautifulSoup file or run it (and the others) against something complex like PySide or SQLAlchemy and see how they compare. I personally am disappointed that it didn't catch all the issues I was looking for. I think for my purposes, I'll be sticking with pylint. This might be a handy tool for a quick and dirty test or just to make you feel better after a particularly poor result from a pylint scan.
Copyright © 2024 Mouse Vs Python | Powered by Pythonlibrary