On Monday 06 September 2010 11:09:08 Sylvain Thénault wrote: > > c) deal with 'print' as a function and the other modifications > > I don't think we need anything special to deal with print as a > function. It will simply be treated as other functions.
right, we have no visit_print method in pylint anyway > > 3) pylint; make tests pass with py3k, write new visit_* methods and > > test... > > there should be no need for new visit_* methods, beside if we want > new functionnalities. Well, the minimal Pylint-3k program could indeed consist of just make pylint run against python >= 3.0. Soon enough though, Pylint-3k should check new functionalities like "nonlocals", handle set generators, take into account Extended Iterable Unpacking: "a, *rest, b = stuff" though, maybe all that will be astng's job... > > Fully Automated conversion will not work. We have more than syntactic > > changes to do: we have different trees with new nodes, nodes that > > disappear... > > We already deal with this kind of pb with different python versions, so > that should not be the show stopper. Well, what I meant is that just running 2to3 on all modules will definitely not be possible. We will have to implement at least the convenient astng nodes with inference methods and the like. But maybe that's the main job after all (except that a lot of tests will have to be adapted) -- Emile Anclin <[email protected]> http://www.logilab.fr/ http://www.logilab.org/ Informatique scientifique & et gestion de connaissances _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
