..@gmail.com
>
>
>> -Original Message-
>> From: Doug Hellmann [mailto:d...@doughellmann.com]
>> Sent: Friday, June 9, 2017 12:34 PM
>> To: openstack-dev
>> Subject: Re: [openstack-dev] [all] Call for check: is your project ready for
>> pylint 1.7.1?
t: Friday, June 9, 2017 12:34 PM
> To: openstack-dev
> Subject: Re: [openstack-dev] [all] Call for check: is your project ready for
> pylint 1.7.1?
>
> Excerpts from Akihiro Motoki's message of 2017-06-09 03:53:34 +0900:
> > Hi all,
> >
> > Is your project r
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 m
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 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 p
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],
> Howev
Is there a driving reason why this has to be done in the Pike cycle? The
requirements freeze is coincident with Pike-3 and your two week deadline
puts it pretty close to that date so I'm going to assume that you will have
to make this change before p3.
Trove is another of the projects that went d
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
