Re: [code-quality] Some other additions to PyCQA possibly

2018-04-21 Thread Carl Crowder
Hi Carlos, I am definitely keen to add more maintainers. If you are interested - and the same is true for anyone on this list - just drop me an email and we can discuss :-) Carl On 20/04/2018 23:31:59, Carlos Coêlho wrote: Awesome Carl! Are there any plans on opening new spots for prospector

Re: [code-quality] Some other additions to PyCQA possibly

2018-04-20 Thread Carlos Coêlho
Awesome Carl! Are there any plans on opening new spots for prospector maintainers? On Fri, Apr 6, 2018 at 8:24 PM Ian Stapleton Cordasco < graffatcolmin...@gmail.com> wrote: > Woot!!! > > On Fri, Apr 6, 2018 at 5:37 PM, Carl Crowder > wrote: > > Hi there, > > > > Finally got around to moving th

Re: [code-quality] Some other additions to PyCQA possibly

2018-04-06 Thread Ian Stapleton Cordasco
Woot!!! On Fri, Apr 6, 2018 at 5:37 PM, Carl Crowder wrote: > Hi there, > > Finally got around to moving this. Since it's so tightly tied to > Landscape.io I wasn't quite sure the best way to do it but that project is > EOL really. Finally made the leap. > > Prospector is now under PyCQA. > > Che

Re: [code-quality] Some other additions to PyCQA possibly

2018-04-06 Thread Carl Crowder
Hi there, Finally got around to moving this. Since it's so tightly tied to Landscape.io I wasn't quite sure the best way to do it but that project is EOL really. Finally made the leap. Prospector is now under PyCQA. Cheers, Carl On 22/03/2018 01:48:06, Carlos Coêlho wrote: Any news on moving

Re: [code-quality] Some other additions to PyCQA possibly

2018-03-21 Thread Carlos Coêlho
Any news on moving prospector to PyCQA? Em 8 de mar de 2018, à(s) 21:06, Carl Crowder escreveu: > I would say that the motivation of pylint-plugin-utils was twofold: > > 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 i

Re: [code-quality] Some other additions to PyCQA possibly

2018-03-08 Thread Carl Crowder
I would say that the motivation of pylint-plugin-utils was twofold: 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. Second - it was re

Re: [code-quality] Some other additions to PyCQA possibly

2018-03-08 Thread Ashley Whetter
Does it make more sense to try and merge pylint plugin utils into pylint core?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.I've been taking a look at this repository recently for

Re: [code-quality] Some other additions to PyCQA possibly

2018-03-08 Thread Claudiu Popa
Hi Carl, From my point of view, they could all live in the organisation, at least pylint-plugin-utils and prospector still seem useful to folks. On Thu, Mar 8, 2018 at 6:58 PM, Carl Crowder wrote: > Hi there, > > There are a few other things that came out of the ashes of Landscape.io that > may

[code-quality] Some other additions to PyCQA possibly

2018-03-08 Thread Carl Crowder
Hi there, There are a few other things that came out of the ashes of Landscape.io that may or may not make sense to move into PyCQA too: 1) pylint-celery - this one I don’t think anyone uses and it isn’t very useful anyway 2) pylint-plugin-utils - this is used by pylint-django and pylint-celery a