Thanks, Sean. I will heartily second that request/proposal.
-amrith -amrith -- Amrith Kumar Phone: +1-978-563-9590 On Fri, Jun 9, 2017 at 11:07 AM, Sean Dague <[email protected]> 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 [1], > > However, some projects (at least neutron) are not ready for pylint > > 1.7.1 and it was reverted [2]. > > it is reasonable to give individual projects time to cope with pylint > 1.7.1. > > > > 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 [3]. As far as I checked, most rules are reasonable > > and worth enabled. > > > > Thanks, > > Akihiro Motoki > > > > [1] https://review.openstack.org/#/c/470800/ > > [2] https://review.openstack.org/#/c/471756/ > > [3] 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 > > -- > Sean Dague > http://dague.net > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
