On Thu, Aug 12, 2010 at 10:58 PM, Sylvain Thénault < [email protected]> wrote:
> On 12 août 16:02, Dan Stromberg wrote: > > On Thu, Aug 12, 2010 at 2:08 PM, Shashwat Anand < > [email protected]>wrote: > > > On Fri, Aug 13, 2010 at 2:33 AM, Tshepang Lekhonkhobe < > [email protected]>wrote: > > > > > >> Hi, > > >> > > >> So where do I start if I want Pylint ported to Py3k? Is there a branch > > >> somewhere? > > >> > > >> > > > I have no idea. But please do so. It is _needed_. > > > > > I agree that it's badly needed. > > > > For starters, you could probably look over the various changes in 3.0 and > > 3.1, and compile a list of what needs to change in the code. > > > http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=list+of+changes+in+python+3 > > > > >From there, the changes could probably be prioritized, and coded one by > one > > or in parallel. > > IMO, we should rather start launching the 2to3 transformer on pylint and > its > dependencies Not at all unreasonable, though we'll probably end up passing through a stage where we have something that runs on Python 3 and checks Python 2 (except during introspection, which would probably be a hybrid) initially. I'm fine with that. > , and at first see what can be made to avoid things it doesn't > deal with. As I see it, the ideal solution would be a purely generated py3k > branch (eg no manual changes needed), but I've no experience yet with the > 2to3 > tool and doesn't know if this is possible (I doubt it is actually, at least > for > lib such as logilab-astng). > I've converted one (other) project using 2to3 so far. I went the route of running 2to3 and then making manual changes after that to fix up the remaining problems - mostly due to strings vs unicode issues. What do the owners of the code think about attempting to come up with a version that runs on (though not _necessarily_ against) 2.6, 2.7 and 3.x unmodified? This would almost certainly mean this new version would not run on 2.5.x. And we can at least do 3 tasks in parallel: make pylint, logilab-astng and > logilab-common > py3k compliant... Agreed. This appears to be a quite nice URL about porting from python 2.x to 3.x: http://wiki.python.org/moin/PortingPythonToPy3k I have a -=Little=- bit of available time (probably just an hour or few on Tuesdays and Fridays), and I can't think of many projects that would be more useful that time into than a py3k version of pylint. It looks like the code is checked into mercurial? Here're some cheat sheets about using mercurial: http://mercurial.selenic.com/wiki/QuickReferenceCardsAndCheatSheets I've checked out the sources with: hg clone http://www.logilab.org/hg/pylint hg clone http://www.logilab.org/src/logilab/astng hg clone http://www.logilab.org/src/logilab/common I've done a lot with Subversion (including administration), but I've not done much with Mercurial yet. Is it important to start py3k branches of each of these before we embark on porting? Or is it just as well to get started against these URL's? In subversion, we'd probably want to branch before starting to make changes. Sylvain, you mentioned you had a py3k branch for logilab-common. May I ask what the URL to it is? And could this same resource be used for astng and pylint branches for python 3k? -- Dan Stromberg
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
