On 21/12/2013 08:18, Dan Stromberg wrote:
On Fri, Dec 20, 2013 at 9:34 PM, Mark Lawrence <breamore...@yahoo.co.uk> wrote:
On 20/12/2013 14:19, Roy Smith wrote:
http://xkcd.com/1306/
I believe that to be a very superficial like. They're unlike in that once
C++ people have compiled their code they can head down to the pub, but
Python people have to stay at work testing because the compiler hasn't
caught all potential errors.
Python should be used with static analysis (EG pylint), IMO, for
reliability. Python should also be used, IMO, with a good set of
automated unit, integration and system tests.
I use the Pydev plugin for Eclipse and have Pylint turned on so that it
automatically checks my code as I type, just awesome. To me your second
sentence above goes without saying. And add in anything that can help
improve quality. This recipe
http://code.activestate.com/recipes/578793-more-strict-unittests-using-a-validator/
only went up yesterday, haven't checked it out in detail but the idea
seems impressive.
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
--
https://mail.python.org/mailman/listinfo/python-list
