Ross, I've been running pylint on a RHEL5 VM to help catch those problems,
but I always had some problems, until this week I've decided to bite the
bullet and fix them all. My idea now is to send the daily reports to the
mailing list.

The only problem is that this would be useful only after the changes are
already in master.


On Mon, Dec 9, 2013 at 4:25 PM, Ross Brattain <notifications@github.com>wrote:

> In client/lv_utils.py:
>
> > @@ -71,7 +71,7 @@ def vg_ramdisk(vg_name, ramdisk_vg_size,
> >
> >          logging.info("Finding free loop device")
> >          result = utils.run("losetup --find", verbose=True)
> > -    except error.CmdError, ex:
> > +    except error.CmdError as ex:
>
> I was going to recommend using pyqver.py
> https://github.com/ghewgill/pyqver to check for 2.4 syntax compatibility,
> but it doesn't catch this case. The only tool I know of which catches this
> case is a the proprietary Pycharm python syntax checker.
>
> It might be possible to add a flake8 plugin to catch this.
> https://github.com/jcrocholl/pep8/blob/master/docs/developer.rst#contribute
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/autotest/autotest/pull/770/files#r8206579>
> .
>



-- 
Lucas