[Python-projects] pylint, pyreverse : mandatory "package" noti n Hg repository? => Fixed + next step?

[Sylvain =?UTF-8?Q?Th=E9nault?=]

On Thu, Oct 18, 2007 at 10:51:08AM +0200, Laurent Bertaud wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> > Removing this dependency on pyxml in favor of elementtree would be a
> > good thing, by the way.  ElemenTree is part of python2.5's standard
> > library, and can be downloaded from
> > http://effbot.org/zone/element-index.htm if you're using another version
> > of python.
> in my ~/GLo directory, I have four directories :
> astng, common, pylint, pyreverse an a link python -> /usr/bin/python2.5
> I am using both python2.4 and python2.5 through debian standard packages
> of Debian/Lenny.

actually to make it works you should mimic the hg layout and put both
common and astng directory in a "logilab" directory. You will have to
create the logilab/__init__.py file manually (touch is enough) so that
python recognize the directory as a package.

> I think my next step will be to test pylint and pyreverse with the
> provided examples and then, according what it is written above, have
> a look on how to remove the pyxml dependency.
> According to you, would it better beginning with a first bug fix or
> the dependency removal?

My 2 cents: first you should be aware that currently pylint is a much
more active project than pyreverse. Official pyreverse version is
outdated for a while now and the repository version include some fixes
but doesn't make it a very used project. So by working on pylint you will
be provided more community support (this include advises, support,
feedback...) and this is certainly more gratifiant. Of course we would
help you as well if you wish to work on pyreverse, but this is more a
heavy rearchitecturing job that you'll have to stand on your own if you
want to get it successful and gain some interest back from the comunity.
Also brain hackers may be interested in working on the pylint/pyreverse
underlying lib, astng, for instance to enhance inference capabilities,
work on 2.5 compatibility...

I think the best would probably to pick some easy bugs in the pylint/astng
trackers to begin digging in the code :) Of course I can tell you which
one sounds easy to me if you want ;)

Also notice that you may get some information on pylint architecture 
(maybe even pyreverse as well) by searching in thie mailing-list archives.
  
-- 
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