On Dec 3, 10:09 pm, Tim Lahey <[EMAIL PROTECTED]> wrote:
> Hi,
Hi Tim,
> Now that Python 3.0 has finally been released
> (http://www.python.org/download/releases/3.0/)
>
> it may be a good idea to start looking for
> incompatibilities in the standard Sage code
> (as compared to those where other packages are
> pulled it).
We will likely upgrade to Python 2,6 first. It will be a while until
all the Python components we include work with Python 3.0 and I doubt
people around want to do all the work. There also has to be a clear
benefit of switching to Python 3.0 - we don't do it just because we
can :)
> I realize that we haven't started with 2.6, but
> it's probably not a bad idea.
One of the main issues with be numpy/scipy here. numpy 1.3 will add
support for Python 2.6, but I have no clue when they will support 3.0.
> Thoughts?
>
> Cheers,
>
> Tim.
Cheers,
Michael
> ---
> Tim Lahey
> PhD Candidate, Systems Design Engineering
> University of Waterloohttp://www.linkedin.com/in/timlahey
>
> smime.p7s
> 3KViewDownload
--~--~---------~--~----~------------~-------~--~----~
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://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
