Excerpts from Akihiro Motoki's message of 2017-06-09 03:53:34 +0900: > 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/ >
I thought we had linters in a list that didn't require the versions to be synced across projects, to allow projects to update at their own pace. Did we undo that work? Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
