On Sep 11, 2007, at 6:11 AM, David Harvey wrote: > On Sep 11, 2007, at 8:59 AM, Jaap Spies wrote: > >> >> Hamptonio wrote: >>> Many of you are probably already aware of this, but there is an >>> early >>> alpha release of python 3000 that came out a couple of weeks ago. I >>> thought that might be worth pointing out now so folks can take a >>> look >>> and get used to it early. The final release is tentatively >>> scheduled >>> for late 2008: >>> >>> http://www.python.org/download/releases/3.0/ >>> >>> I would think most of the python in sage is relatively clean code >>> that >>> won't need a lot of changing, but it will help if we avoid conflicts >>> now. >>> >> >> There is a tool for translating existing code to Python 3k. >> http://svn.python.org/view/sandbox/trunk/2to3/ >> >> And in Python-2.6 (not yet released) there will be code to isolate >> known issues. > > What I'm more worried about is cython compatibility, especially if > python internals have changed a lot.
Me too... It looks like 2.x is going to be around for a while though, so we'll hopefully have time to transition. I'm not looking forward to having to have a 2.x and 3.x branch of Cython :-( --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---