Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Gareth wrote: Thanks for all! However I'm developing on stable/liberty and it failed with running "tox -e pep8" because of this issue. And I found it is pylint==1.4.5 on master branch. Could we cherry-pick this test-requirements update back to stable/liberty? Try

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

ot be updating this in the requirements project? >> >> From: Paul Michali <p...@michali.net> >> Reply-To: OpenStack List <openstack-dev@lists.openstack.org> >> Date: Tuesday, December 1, 2015 at 4:50 PM >> To: OpenStack List <openstack-dev@lists.openstack.org&

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

50 PM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage Some additional info... astroid upstream folks are going to try to push for pylint 1.4.5 that pins to astroid 1.3.8

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Some additional info... astroid upstream folks are going to try to push for pylint 1.4.5 that pins to astroid 1.3.8. If that happens, we could just pin pylint at 1.4.5. Ref: https://bitbucket.org/logilab/astroid/issues/275/140-and-141-fail-to-work-with-pylint-144 It sounds like we don't need to

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Reply-To: OpenStack List <openstack-dev@lists.openstack.org> > Date: Tuesday, December 1, 2015 at 4:50 PM > To: OpenStack List <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage > > Some additional info... > > a