from
Nicolas Chauvat <nicolas.chauvat at logilab dot fr>
to
Gustavo J. A. M. Carneiro <gjc at inescporto dot pt>
subject
Re: [Python-projects] pylint: Warning about relative imports
date
On Wed, Oct 19, 2005 at 10:31:37PM +0100, Gustavo J. A. M. Carneiro wrote:2005/10/20 00:08
> I'm baffled by excessive zealous of pylint.
Pylint can be quite a zealot indeed, but only if you let it be so. It
is *meant* to check as many different things as possible then let you
configure it to your needs. You may have almost everything turned on
by default, but that doesn't mean you have to keep it that way, so
just write the pylintrc that fits your need and your team's habits.
> It makes no sense to warn about something that absolutely cannot be
> done any other way. Anyway, sorry, but it wasn't clear to me how to
> disable this; that's why I asked.
We chose to forbid relative imports in the code we write at Logilab. I
do not think we had any problem with that. But then again, if you want
to use relative imports, who will forbid you? Neither I nor pylint!
> One other thing that I don't understand is when pylint warns about
> calling a function with keyword arguments, like func(foo=bar). But now
> I can't reproduce the problem anymore.. maybe it was in an older version
> of pylint.
pylint can warn you about uses like func(*foo) or func(**bar).
Happy linting.
--
Nicolas Chauvat
logilab.fr - services en informatique avancée et gestion de connaissances
_______________________________________________
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects