from
Sylvain Thénault <sylvain.thenault at logilab dot fr>
to
Fabio Zadrozny <fabioz at esss dot com dot br>
subject
[Python-projects] Re: FW: PyLint 0.6 bug
date
On Friday 21 January à 11:39, Fabio Zadrozny wrote:2005/01/21 14:44
> Hi Sylvain, remember me?
Hi Fabio
> I just updated to version 0.6, but I'm still unable to use it.
>
> E.g. If I have the code below:
>
> from qt import *
>
> class C(QWidget):pass
>
>
>
> I'm getting the traceback posted below.
>
> The thing is qt is actually defined as a dll
> (C:\bin\Python23\Lib\site-packages\qt.pyd), so, there is no way you could
> get its ast (you MUST import it to get its tokens) - I had the same problem
> for doing code completion for the pydev editor. I based my solution on
> having the concept of an AbstractModule (that had the logic exposed),
> CompiledModule and SourceModule... (maybe you can also work on that idea),
> as for you (I believe) you just want compiled module tokens to see if they
> exist and not anything else.
Actually yes, I've to import compiled modules to inspect them. But
that's just the way the ast is builded which changes, usually pylint
doesn't have to know about it.
> I believe this would happen using any compiled module, but have not tested
> for others...
Hum, did you update common libraries too ? Your sample code is correctly
analyzed on my [linux] computer.
--
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