This SEP has already been completed.
Switching Sage to Python 2.6.x
Sage currently uses Python 2.5.2 + patches. Python 2.6.1 was release on December 4th, 2008. We ought to migrate to it. There are some compatibility issues with various python based spkgs. We should update to Python 2.6 since it is the currently latest 2.x branch and has some bug fixes over 2.5.4, i.e. it works better on OSX 10.6 and builds with non-Apple gccs on OSX to name just two issues. Below should be a growing list of those with remarks if they work with python 2.6.x or if there are any issues.
- numpy: Sage 3.4 ships numpy 1.2 which does not have official Python 2.6 support, but 1.3 has been released which does.
matplotlib: Ought to work - see http://sourceforge.net/mailarchive/forum.php?thread_name=49DE427C.1080600%40stsci.edu&forum_name=matplotlib-devel
I did a lot of the initial fixes for Python 2.6 within the first week of the 2.6.0 release -- they were mostly of the warning/style nature. I've been running it on 2.6 on and off ever since, so it should be ok. But let us know if you find anything. Cheers, Mike Adam Mercer wrote: > On Sun, Apr 5, 2009 at 16:01, David Moore <[email protected]> wrote: > > >> I've had matplotlib running fine on Python 2.6 since shortly after the Python >> 2.6 release. I run Arch Linux. Are you perhaps looking for Windows builds? >> Or does your distro not have matplotlib compiled for Python 2.6 yet? >> > > No, I'm looking to package matplotlib for python-2.6 on MacPorts and > wanted to check that there would be no unexpected surprises, but from > the above it sounds like all should be good. > > Cheers > > Adam
- NetworkX: known issues in latest upstream (0.99CVS). Sage ships NetworkX 0.99, but there are some problems in the spkg.
- Sympy: Known to be working with Python 2.6 since at least some 0.6.x release. Regularly tested with Python 2.6 to assure that it keeps working. Sage 3.4.1 will ship Sympy 0.6.4.