[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Standardizing our Python code style

From: Barry Scott <barry_at_barrys-emacs.org>
Date: Sat, 24 Oct 2009 08:59:07 +0100

On 22 Oct 2009, at 19:37, Bhuvaneswaran A wrote:

> All sounds like an excellent checklist to me.
> I'd also go 1 step ahead and use pylint tool to validate all our
> python
> scripts. We may have a pylintrc configuration file in our repository
> that defines all these standards (and more) as a rule. We may have a
> benchmark for pylint score (10/10?) for any python script that goes in
> the repository! -:)

My experience with pylint is that it raises a huge number of false
and false negative reports. These need human filtering to find the gems.
Also beware that pylint imposes style checks that may well conflict with
subversions coding style.

Only trivial code will pass clean.

pychecker is better, but not perfect either.


Received on 2009-10-24 09:59:28 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.