from
Sylvain Thénault <sylvain.thenault at logilab dot fr>
to
Greg Wilson <gvwilson at cs dot utoronto dot ca>
cc
Sylvain Thénault <sylvain.thenault at logilab dot fr>
subject
PyLint / PyChecker unification
date
On Sunday 11 September à 14:15, Greg Wilson wrote:2005/09/12 10:38
> Hi Sylvain,
Hi Greg,
I'm only answering now since I'm just right back from holidays :)
> Any thoughts on my previous message re combining PyLint and PyChecker?
Well, yes. First, I did try to start a discussion about this on c.l.py a
few month ago, without any reactions, even from the main pychecker
author (maybe did you emailed him to nad had more luck than I add ?).
After that, there is two things which makes me doubt about any
unification, at least in a near future :
* project's goal: pychecker is looking for bugs, while pylint is
looking for bug *and* bad style code (pythonically or more generaly
programaticaly related). Today pychecker is still finding more bugs
than pylint, and of course I would like pylint to get them, but don't
hurry to implement related checks since pychecker does them...
* project's implementation: they are radically different, since
pychecker is working on living (ie imported) code, while pylint is
working on a syntax tree representation (ie only parsed). This implies
that an unification requires a rewrite of one of the two projects :(
When I started pylint, I've of course begun by taking a look at
pychecker source code, but I've been really disappointed by the lack of
documentation and the obscurness of it which has discouraged me to
extended it, and so led me to write another full new project. IMO (biased
of course ! ;), pylint code is clean, well designed and documented (in
the source).
my 0.2 euros,
--
Sylvain Thénault LOGILAB, Paris (France).
http://www.logilab.com http://www.logilab.fr http://www.logilab.org
PS: cc'ing python-projects since that my interest other people