<div dir="ltr"><div style="font-family:courier new,monospace" class="gmail_default">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.<br><div class="gmail_default" style="font-family:courier new,monospace"><br></div>Trove is another of the projects that went down in flames with the new pylint and I'm wondering what benefit this has for projects in general. The notion of accumulating more technical debt (enable pylint 1.7.1 and disable the new tests, cleanup code later) strikes me as less than ideal.<br><br></div><div style="font-family:courier new,monospace" class="gmail_default">Thanks,<br><br></div><div style="font-family:courier new,monospace" class="gmail_default">-amrith</div><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><span style="font-family:courier new,monospace"></span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">-amrith</span><br><br><span style="font-family:courier new,monospace">--</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">Amrith Kumar</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">Phone: +1-978-563-9590</span><br><br></div></div>
<br><div class="gmail_quote">On Thu, Jun 8, 2017 at 1:53 PM, Akihiro Motoki <span dir="ltr"><<a href="mailto:amotoki@gmail.com" target="_blank">amotoki@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Is your project ready for pylint 1.7.1?<br>
If you use pylint in your pep8 job, it is worth checked.<br>
<br>
Our current version of pylint is 1.4.5 but it is not safe in python 3.5.<br>
The global-requirements update was merged once [1],<br>
However, some projects (at least neutron) are not ready for pylint<br>
1.7.1 and it was reverted [2].<br>
it is reasonable to give individual projects time to cope with pylint 1.7.1.<br>
<br>
I believe bumping pylint version to 1.7.1 (or later) is the right<br>
direction in long term.<br>
I would suggest to make your project ready for pylint 1.7.1 soon (two<br>
weeks or some?)<br>
You can disable new rules in pylint 1.7.1 temporarily and clean up<br>
your code later<br>
as neutron does [3]. As far as I checked, most rules are reasonable<br>
and worth enabled.<br>
<br>
Thanks,<br>
Akihiro Motoki<br>
<br>
[1] <a href="https://review.openstack.org/#/c/470800/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/470800/</a><br>
[2] <a href="https://review.openstack.org/#/c/471756/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/471756/</a><br>
[3] <a href="https://review.openstack.org/#/c/471763/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/471763/</a><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div><br></div>