On Mon, Aug 16, 2010 at 11:02:00AM +0200, Sylvain Thénault wrote: > On 14 août 13:07, Dan Stromberg wrote: > As a code checker, pylint is expected to run on as many version as possible. > We only recently dropped 2.2 support. IMO, dropping support for python <= 2.4 > is fine (and allow a big cleanup in astng, since we currently have to deal > with > two underlying ast representation), though I would like to keep the 2.5 > support. > What pb do you see with it? > > > This appears to be a quite nice URL about porting from python 2.x to 3.x: > > http://wiki.python.org/moin/PortingPythonToPy3k > > Nice. I've added this link to the ticket regarding the port of pylint to > python 3.
Mercurial has also started it's python3 port and face similar compatibility constraits. The google summer of code student working on it has report is experience on they wiki. http://mercurial.selenic.com/wiki/Py3kPort -- Pierre-Yves David
signature.asc
Description: Digital signature
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
