from
Adrien Di Mascio <adrien.dimascio at logilab dot fr>
to
Neal Norwitz <nnorwitz at gmail dot com>
cc
Sylvain Thénault <sylvain.thenault at logilab dot fr>
subject
Re: [Python-projects] Re: PyLint / PyChecker unification
date
Hi all,2005/09/13 08:33
On Mon, Sep 12, 2005 at 10:56:17AM -0700, Neal Norwitz wrote:
> On 9/12/05, Sylvain Thénault <sylvain.thenault@logilab.fr> wrote:
> > On Monday 12 September à 08:25, Greg Wilson wrote:
> My biggest concern is actually with using the compiler package in the
> python library. It doesn't parse all code and can be quite slow from
> previous experiments (perhaps the situation is different now, I don't
> really know). In general, compiler isn't maintained well enough. I
> was hoping that the AST branch in python would bear more fruit, but
> that isn't really making progress either. So I have some outstanding
> issues in my own mind about how to move forward.
Just to mention that PyPy might provide some help here, if not right
now, maybe in a few weeks/months. One of the last focus in PyPy was to
work on a Python version of the parser and the compiler, and it was
an occasion to improve a bit and fix the compiler package. These fixes
are still not backported to the compiler package, but they will be
soon, hopefully.
Another option might be to directly use the PyPy interpreter, and
write a specific ObjectSpace for PyLint / PyChecker.
just my 2 cents,
Cheers,
Adrien.
--
Adrien Di Mascio
LOGILAB, Paris (France).
http://www.logilab.com http://www.logilab.fr http://www.logilab.org