<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Any news on moving prospector to PyCQA?<br><div><br>Em 8 de mar de 2018, à(s) 21:06, Carl Crowder <<a href="mailto:carl.crowder@gmail.com">carl.crowder@gmail.com</a>> escreveu:<br><br></div><blockquote type="cite"><div><style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I would say that the motivation of pylint-plugin-utils was twofold:</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">First - it was a bit of a pain to try to figure out how to write a plugin. This was about 5 years ago though so not sure if that is still true but it took me a while to figure out. Docs on that could be better.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Second - it was really just a utility to make it easier to do several things which were useful, such as “skip this error in this context” or “add this error in this context”.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I definitely think the plugin API in pylint could be easier to use, I’m not sure if pylint-plugin-utils is the answer because it’s just a bandaid really. It could be useful to see the symptoms it was trying to solve though.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Carl</div> <br> <div id="bloop_sign_1520553742008413952" class="bloop_sign"></div> <br><p class="airmail_on">On 8 March 2018 at 21:51:29, Ashley Whetter (<a href="mailto:ashley@awhetter.co.uk">ashley@awhetter.co.uk</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>
<title></title>
<div dir="auto">Does it make more sense to try and merge pylint
plugin utils into pylint core?
<div dir="auto">If the plugin interface is clunky enough on its own
that there exists utilities for creating plugins, then I think
that's an issue that we need to look at resolving.</div>
<div dir="auto">I've been taking a look at this repository recently
for the per directory config project in pylint to get sense of how
the plugin interface is being used and getting ideas for the kind
of thing that we should be aiming for.</div>
<div dir="auto"><br></div>
<div dir="auto">Ashley</div>
</div>
</div></div></span></blockquote>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>code-quality mailing list</span><br><span><a href="mailto:code-quality@python.org">code-quality@python.org</a></span><br><span><a href="https://mail.python.org/mailman/listinfo/code-quality">https://mail.python.org/mailman/listinfo/code-quality</a></span><br></div></blockquote></body></html>