<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 19, 2015 at 10:59 PM Lucas Meneghel Rodrigues <<a href="mailto:lookkas@gmail.com">lookkas@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Thu, Nov 19, 2015 at 5:49 PM Alan Evangelista <<a href="mailto:alanoe@linux.vnet.ibm.com" target="_blank">alanoe@linux.vnet.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<font size="-1">I have noticed avocado and avocado-vt don't pass
pylint (1.4.3) validation. Do you guys use any static code checker
during development and testing in Travis CI? <br>
<br>
If not, is there a reason why not? I use Pylint in all my Python
projects and it helps me a lot to detect bugs early, before
running test suites. A patch which makes code pass Pylint (or
other static code checker of your choice) validation would be
viable and desired?<br><br></font></div></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>I take personal offense by the thought that avocado and avocado-vt are not being regularly pylinted.</div></div></div></blockquote><div><br></div><div>^ Oh, by the way, I was joking there :) </div></div></div>