[Python-projects] PyLint Where does one report an apparent bug?

[Sylvain Thénault]

On Sunday 25 February à 12:12, Colin J. Williams wrote:
> 
> Sylvain Thénault wrote:
> 
>     On Friday 23 February à 14:46, Colin J. Williams wrote:
> 
> 
>         Could you let me know please?
> 
>         Colin W.
> 
>         Calling PyLint from PyScripter, we get error output.
> 
>         Using the command line, we get the same traceback:
> 
> 
> 
>     which version of logilab-astng are you using ? this seems to be a py 2.5
>     specific bug which has been fixed in astng 0.16.1.
> 
> Sylvain,
> 
> Many thank for your reply.
> 
> I have astng-0.16.0, which I had downloaded quite recently.
> 
> I have now installed astng-0.16.3 and get the same problem.
> 
> It seems that raw_building.py was, according to line 24, last revised last year
> - 5-Mar-06.
> 
> Should I be going back to 0.16.1?

huum, the date in the file is wrong, and I don't think you should go
back to a previous version. I've checked the code of astng 0.16.3 and
the fix I was thinking about was actually in. I can think about two
things causing you this problem :

- an installation problem on your side causing  the old version of astng
  still being used. What's the output of "pylint --version" ? I don't
  known how to check versions used inside pyscripter though...

- the wrong version of the "attach_import_node" function is used for an
  unknown reason (yet :). You can check this by adding a print or
  whatever around the "if/else" switch on line 49/57 of raw_building.py

PS: I'm switching the discussion to the python-projects at logilab.org
    mailing list which is the right place to discuss pylint/astng
-- 
Sylvain Thénault                               LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian:  http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
Python et calcul scientifique:           http://www.logilab.fr/science