[openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?
amrith.kumar at gmail.com
Fri Jun 9 16:09:40 UTC 2017
I will heartily second that request/proposal.
On Fri, Jun 9, 2017 at 11:07 AM, Sean Dague <sean at dague.net> wrote:
> On 06/08/2017 02:53 PM, Akihiro Motoki wrote:
> > Hi all,
> > Is your project ready for pylint 1.7.1?
> > If you use pylint in your pep8 job, it is worth checked.
> > Our current version of pylint is 1.4.5 but it is not safe in python 3.5.
> > The global-requirements update was merged once ,
> > However, some projects (at least neutron) are not ready for pylint
> > 1.7.1 and it was reverted .
> > it is reasonable to give individual projects time to cope with pylint
> > I believe bumping pylint version to 1.7.1 (or later) is the right
> > direction in long term.
> > I would suggest to make your project ready for pylint 1.7.1 soon (two
> > weeks or some?)
> > You can disable new rules in pylint 1.7.1 temporarily and clean up
> > your code later
> > as neutron does . As far as I checked, most rules are reasonable
> > and worth enabled.
> > Thanks,
> > Akihiro Motoki
> >  https://review.openstack.org/#/c/470800/
> >  https://review.openstack.org/#/c/471756/
> >  https://review.openstack.org/#/c/471763/
> Please only make changes like this in the first milestone of the cycle.
> Lint requirements changes are distracting, and definitely shouldn't be
> happening during the final milestone.
> Sean Dague
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev