will have anything interesting to say.
>
> The maintainers you might want to interview are Carl Crowder or Carlos Coelho.
>
> Best,
> Pierre
>
> Le mar. 26 oct. 2021 à 20:59, Ian Stapleton Cordasco
> a écrit :
>>
>> Not sure that it's very actively maintained. I&
Hi all, especially Stéphane and David,
I'm the original creator of the prospector tool so it's my fault that
it has become unmaintained. I did find a maintainer a while ago who
did a fantastic job keeping it going but I assume they're now no
longer able to and I had kind of fallen out of love with
There is already SARIF (http://sarifweb.azurewebsites.net/) but I don't think
it's been adopted by anything. I like the idea though.
On 08/01/2021 00:44:10, Ian Stapleton Cordasco
wrote:
___ code-quality mailing list --
code-quality@python.org To unsu
I'd guess what you're looking for is Levenstein distance.
On 15/09/2019 22:26:56, Alexander Todorov wrote:
Hi folks,
I am looking for some tool (or algorithm which I can implement at the worst)
which calculates similarities between strings. I would turn this into a pylint
plugin b/c this is how I
I think that this would be better a pylint specific issue on github
Also I think this would be quite hard - it seems you want a check that says 'if
this is a function that is used in a boolean but it it not called' that seems
quite specific and you never know, if it's not a syntax error, perhaps
maintainers?
On Fri, Apr 6, 2018 at 8:24 PM Ian Stapleton Cordasco
mailto:graffatcolmin...@gmail.com]> wrote:
Woot!!!
On Fri, Apr 6, 2018 at 5:37 PM, Carl Crowder mailto:carl.crow...@gmail.com]> wrote:
> Hi there,
>
> Finally got around to moving this. Since it'
on moving prospector to PyCQA?
Em 8 de mar de 2018, à(s) 21:06, Carl Crowder mailto:carl.crow...@gmail.com]> 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
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
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
Hi all,
I’ll be quick - I think pylint-django is better under PyCQA! If you agree I
will help out wherever necessary
I built it out of a hope I could help bring pylint to Django users so I
hope that has helped, people seem to use it so I hope moving it to PyCQA
helps users of it too!
Carl
__
Hi all, author of Prospector here.
It's definitely not an alternative to pylint or flake8, it's just a
convenience wrapper. The entire point was just to make it a bit easier
to get started as not everyone wants to spend the time configuring
every tool. The idea is to be a "gateway drug" to bridge
I added this to prospector by allowing inheritance, so that your
custom directives could inherit from premade ones that come as part of
the library or 'project-wide' ones that you make but want to tweak on
a per-codebase level:
http://prospector.readthedocs.org/en/master/profiles.html#inheritance
Hi Skip,
This kind of argument was on my mind a little when I made prospector
(https://github.com/landscapeio/prospector) although probably from a
different angle. There are many tools out there and using them all
means you can get the maximal coverage of all concepts, with some
overlap. Each tool
I think it's a good idea. I personally dislike contributing to
hg-based projects because it's such a faff for me compared to using
git, and I wouldn't be surprised if others are put off contributing
for a similar reason (not that I'm saying the reason is good, I'm just
lazy!)
__
Hi,
I will be there, and would love to meet up with you all. I'll be doing
a talk on 'Automated Code Reviews', which is largely based on the
lessons learned from creating https://landscape.io, which builds on
the amazing work you guys have done with pylint!
Carl
On 11 July 2014 18:02, Andrey Vla
I recently asked about the same thing, although there wasn't much discussion as
a result.
Pylint is aware of "from __future__ import print_function" and using it will
suppress this warning you are seeing. However that is not available for Python
2.5, so it depends on what kind of compatibility
Hi all,
I wanted to canvas your opinion about something.
Currently, if you have a print statement with brackets in Python2, pylint will
raise a comment C0325. This is suppressed if "from __future__ import
print_statement" is used.
My question is whether or not using print statements with paren
eak
> else:
> return True
> return False
>
> (Caveat: none of this code has been tested)
>
>
>
>
> On 12 January 2014 07:21, Ian Cordasco wrote:
> Woops. Sorry for the confusion. I never end up using that particular
> construct so I never ge
Ian, it's the opposite - 'else' is only triggered if *no* break statement
is encountered.
On 12 January 2014 16:12, Ian Cordasco wrote:
> I don't see any mesage from pylint in your email, could you post it again?
>
> Regardless, I think what you're disagreeing with is the language
> specificati
This came up once before, and I think the reasoning is that a for loop
without a break statement means the 'else' is redundant.
In your example, you can remove the 'else' and it would be functionally the
same.
On 12 January 2014 15:57, Kay Hayen wrote:
>
> Hello,
>
> often I write code like th
Hi Andrey,
I definitely support some centralized collection of API data, I think it would
be very useful.
How do you plan to support additional libraries? I have been writing a
plyint/astroid plugin for Django for example, which has (very early beginnings
of) the type information you want to
Hi Ian,
I'm interested in helping out, and #99 looks like the easiest place to get
started learning the codebase.
I also like the idea of a pylint plugin.
Carl
On 4 Jul 2013 17:42, "Ian Cordasco" wrote:
> Hey all,
>
> I would first like to apologize for my complete disappearance from
> everyt
22 matches
Mail list logo