> On Mon, 2011-09-05 at 07:32 +0200, Julien Puydt wrote:
> Python is up to version 3.2.2 which is incompatible with 2.7.
> Plus, there is no standard for the language. It is clear that
> Sage is losing ground on the upstream development path. What
> happens when the python-based spkgs, such as SciPy, convert to
> 3.x? The time will come when all published materials about
> Python use 3.x syntax and semantics, at which point Sage will
> no longer be programmed in "Python". It happened to many
> languages (e.g. Fortran, C, Lisp, etc.).
> 
> I don't believe that Python allows you to redefine standard
> Python functions and it doesn't have a macro facility so neither
> path used by Axiom is available for Sage.
> 
> As pointed out in the article, the longer this continues, the
> harder, more expensive, and more disruptive the changes will be.
> 
I can talk about the python upgrade since I have basically took charge
here. Sage is basically currently using python-2.6.4 with some patch.
At the present stage, after some patch that I pushed we probably could 
safely go to 2.6.7. I am currently working on getting sage to python-2.7
and think of it as a first landing point on the way to python-3.
For both python-2.7 and python-3 my opinion is that sage is now the main
drag. All python dependencies of sage work under python-2.7. I cannot think 
from the top of my head of something that doesn't work with python-3,
may be sage-latex...
So, at the present time the big thing preventing us to move to a later python
is sage itself. Once we managed to clean the stuff related to #9958 and 
#11139 we can start cleaning the stuff for python-3. There are a lot of
get/set/delslice that look like dead/unfinished code to me. That would be a 
first step to python-3.

I don't wish to expand too much on upgrading stuff. While we don't want 
to upgrade for the sake of upgrading on the other hand we don't want to
get problem with rot. So keeping up to date should still be done on a regular
basis unless there is a good reason not to.

Francois

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to