Sylvain Thénault wrote, On 03/15/2010 11:56 AM:
On 14 mars 00:40, Mads Kiilerich wrote:
Pylint has a lot of options to controlling the behaviour and output.
But it is my experience that there are so many that they are very
hard to find and use correctly.
do you have some ideas about
On Tuesday 16 March 2010 11:19:17 Emile Anclin wrote:
> I came across your problem a long time ago;
and there was a thread and a ticket about it
http://lists.logilab.org/pipermail/python-projects/2009-June/001945.html
https://www.logilab.net/elo/ticket/9542
Of course, that doesn't help us
On Tuesday 09 March 2010 17:59:02 Giovanni Gherdovich wrote:
hello,
sorry for the late answer, I was not here last week.
I came across your problem a long time ago;
actually, I believe that it worked the right way when I started working on
Pyreverse last year, but it got somewhere broken while
Hi,
Attached is .diff file on a proposed fix for pylint #4581: option to NOT get
a Missing docstring (C0111) warning if a method is overridden.
All I did was:
- add an option, no-docstring-overridden that when invoked
--no-docstring-overridden=y, it won't check the docstring for a method that
is
