William Stein wrote: > On Tue, Jun 2, 2009 at 6:14 PM, Nick Alexander <ncalexan...@gmail.com> wrote: >> >> On 2-Jun-09, at 5:59 PM, Dan Drake wrote: >> >>> On Tue, 02 Jun 2009 at 09:16AM -0700, Nick Alexander wrote: >>>>> Note that Python 2.6 includes a JSON module by default, so we might >>>>> have to deal with these issues sooner or later anyway. >>>> Why are we not using this? (Or a version backported to Python 2.5, >>>> if >>>> that would be needed?) >>> The same guy wrote simplejson and the Python 2.6 json module, so my >>> guess is that simplejson pretty much *is* the backported version. (Or >>> perhaps the json module is the "fowardported" version...) >> I feel most comfortable using the official module when possible. Is >> there any reason not too in this situation? > > Why don't we just upgrade to Python 2.6? If there is anything in > Sage that doesn't work with Python 2.6, we should just fix it. I > can't believe how long we have been waiting to do this.
Your timing is wonderful. Numpy and scipy were major stumbling blocks to getting to python 2.6. Josh Kantor just positively reviewed the numpy 1.3 spkg and a scipy 0.7 spkg. Both of these releases specifically worked on python 2.6 compatibility. As a first step to getting Python 2.6, merge: http://trac.sagemath.org/sage_trac/ticket/3391 http://trac.sagemath.org/sage_trac/ticket/6140 (this needs a slight doctest fix) Thanks, Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
