Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

2017-06-10 Thread Davanum Srinivas
Amrith, "fell on deaf ears" Seriously? It's a double revert and did not have the link to the email thread. hence my +2. It still needed another +2 and +W before it would have been on its way to merging. So the -1's would have stopped that from another requirements person from doing that. --

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

2017-06-10 Thread Amrith Kumar
I guess this mail thread and the questions asked here fell on deaf ears because I see https://review.openstack.org/#/c/472891/1 marching its way to merging. -- Amrith Kumar amrith.ku...@gmail.com > -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Friday,

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

2017-06-09 Thread Doug Hellmann
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

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

2017-06-09 Thread Amrith Kumar
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?

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

2017-06-09 Thread Sean Dague
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], >

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

2017-06-09 Thread Amrith Kumar
​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