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 constrained versions of tox
ts project?
>>
>> From: Paul Michali
>> Reply-To: OpenStack List
>> Date: Tuesday, December 1, 2015 at 4:50 PM
>> To: OpenStack List
>> Subject: Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage
>>
>> Some additional info...
>>
>&
r 1, 2015 at 4:50 PM
> To: OpenStack List
> 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. If that happens, we cou
t;>
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. If that happens, we could just pin pylint at 1.4.5. Ref:
https://bitbucket.org/logilab/astroid/issu
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 p
I found a problem yesterday running pep8 locally in neutron-lbaas. After
discussing with LBaaS team, we identified that there is a problem with
pylint. The same issues were seen, when hecking in neutron and
neutron-vpnaas repos (need to check neutron-fwaas). There are two issues
seen.
First, the
