from
Sylvain Thénault <sylvain.thenault at logilab dot fr>
to
Meding, Olaf <olaf.meding at bruker-axs dot com>
cc
Fabio Zadrozny <fabioz at esss dot com dot br>
subject
Re: [Python-projects] Re: FW: PyLint 0.6 bug
date
On Friday 21 January à 08:50, Meding, Olaf wrote:2005/01/21 16:00
>
> > from qt import *
>
> I can not use PyLint because I am using Python 2.2.1 (we are working on upgrading).
pylint should work with python >= 2.2. If it doesn't, it's a bug.
> However we use Qt extensively. We also use PyChecker, which works great! However, PyChecker has problems with "from qt import *" (lots of bogus warnings). This form of the import statement is bad style anyway because it imports anything. A much cleaner way is to use "import qt". This makes clear what is used from the qt module.
Using both pylint and pychecker is a goog coding habit ! And you're
right that generally using wildcard import is bad since it pollutes your
name space in an uncontrolled fashion.
> Now my question, does PyLint work with Qt? Thanks.
yes, except that it seems to have a litle problem with analyzing of
module using qt on windows platforms, as reported by Fabio Zadrozny in
this thread.
--
Sylvain Thénault LOGILAB, Paris (France).
http://www.logilab.com http://www.logilab.fr http://www.logilab.org
_______________________________________________
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects