I’ve got a question out there for everyone doing Python hacking — does your normal coding cycle include an analysis tool ala Pylint/PyChecker/PyFlakes?
Do you just rely on intelligence in your IDE of choise (Wing, Komodo, Eclipse+PyDev)?
Do you feel the need for the analyzers, or do you “discard” them in favor of writing unit tests/doctests first (personally I don’t find the two exclude one another) to verify functionality over “correctness”.
Which (if any) do you prefer? Do you setup automatic check-in triggers?
Or, do you really take the conformity-to-style-and-rules-correctness to a higher level and auto-pipe checked in code through a PythonTidy?
-
http://www.voidspace.org.uk/python/weblog/index.shtml Michael Foord
-
Matt
-
http://www.ohuiginn.net Dan
-
Pete
-
Brandon Corfman
-
http://gedmin.as Marius Gedminas
-
http://kentsjohnson.com Kent
-
http://kentsjohnson.com Kent
-
Jeff McNeil
-
Jeff
-
Ed Page
-
jnoller
-
jnoller
-
http://pyblog.drbrett.ca Brett
-
Jay
-
Paul Hildebrandt
-
Zachary Voase
-
Zachary Voase