On 17 août 18:47, Dan Stromberg wrote: > On Mon, Aug 16, 2010 at 5:08 AM, Tshepang Lekhonkhobe > <tshep...@gmail.com>wrote: > > Thanks for the great responses. It's a little confusing though, so can > > you guys create some page (wiki?) somewhere on your site on what > > actually needs to be done by a wannabe like me (with a link tothe > > ticket: http://www.logilab.org/ticket/19645). > > > I like this idea - to describe plans and status on a wiki. Does logilab > have a wiki? If not, is using the python wiki for a specific project's > status considered acceptable by the owners of the pylint code and the > maintainers of the python wiki?
Until logilab.org grows its own wiki, and that won't occurs until pylint is ported to py3k (I hope at least ;), it's fine with me. > I believe the basic flow of the port is to install the code, run the unit > tests, and make a note of which tests are passing and which are failing > initially. > > Then run 2to3 on one of the packages, and check the unit tests again - > making sure that they're running on python3 and not python2. Then edit the > source to correct any problems that are new (as identified by the tests), > ideally in a way that will run on 2.5, 2.6, 2.7, 3.0 and 3.1. It's probably > a good idea to have all 5 of these versions installed on your system for > testing during development. > > Then continue similarly for the other two packages. Sounds good to me, the easiest being to start with logilab-common, then logilab-astng, then pylint. Regarding astng, we should start a branch which drop 2.4 support (that should remove a non negligeable part of code that we won't have to port anymore). > Finally, there'll almost certainly be some new features to conditionally > add, and old features to conditionally remove, from what pylint will accept > - so that pylint for python3 doesn't accidentally accept features that are > only in python2, for example. Yup, though I think there won't be a lot of stuff like this since pylint see is behaviour impacted by the python interpreter running it implicitly. The hardest part being to deal with ast representation difference (and astng is responsible to give a common representation / compatibility layer here). -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
