On Tue, Apr 24, 2012 at 10:39:24AM +0800, Lei Li wrote:
> On 04/12/2012 10:48 PM, Saggi Mizrahi wrote:
> >Now that we started moving to conform with pep8 you would probably like to 
> >be able to easily check your code.
> >
> >If you use vim you could use this vim script
> >http://www.vim.org/scripts/script.php?script_id=2914
> I check PEP8 based on this version and it passed with
> no noise.
> But seems it failed to vdsm_unit_test with
> 'E261 at least two spaces before inline comment.'
> And this version can find the E261 error too:
> https://github.com/jcrocholl/pep8/branches/master
> Also I found otherinconsistent  check result from different
> python-pep8 versions.
> So I think It is necessary to have auniformstandard
> for pep8 in vdsm to avoid such noise.

I'd say that the version running in jenkins.ovirt.org is our de-facto
standard (python-pep8-0.6.0-3.fc15.noarch I believe).
vdsm-devel mailing list

Reply via email to