On Friday 09 April 2010 17:37:50 Alexandre Fayolle wrote: > On Friday 09 April 2010 17:03:47 Edward K. Ream wrote: > > On Fri, Apr 9, 2010 at 4:10 AM, Sylvain Thénault > > > > <sylvain.thena...@logilab.fr> wrote: > > > a quick mail to inform you that today is the last day to register > > > on the "porting pylint to py3k" google summer of code project I'm > > > willing to mentor. > > > > Here is a blog entry that may be of interest: > > > > http://edreamleo.blogspot.com/2009/12/converting-leo-to-python-3k-sur > >prises .html > > > > The short summary: given reasonable unit tests, porting is > > straightforward. > > I'm afraid pylint use of some python internals (ast) will give a little > more trouble. But I'd be glad to be proven wrong.
I think, the ast/_ast module in itself is not the problem, but we will have to parse new kind of nodes (Nonlocal, Dict/SetGenerator, Starred (at least for extended literal unpacking), SetComp etc. hence a lot of new 'visit_%' methods in astng and pylint), deal with 'print' as a function, and all the other syntax differences -- Emile Anclin <emile.anc...@logilab.fr> http://www.logilab.fr/ http://www.logilab.org/ Informatique scientifique & et gestion de connaissances _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
