> > 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 :)
Indeed, acoording to http://docs.python.org/dev/whatsnew/2.6.html "The major theme of Python 2.6 is preparing the migration path to Python 3.0, a major redesign of the language. Whenever possible, Python 2.6 incorporates new features and syntax from 3.0 while remaining compatible with existing code by not removing older features or syntax. When it’s not possible to do that, Python 2.6 tries to do what it can, adding compatibility functions in a future_builtins module and a -3 switch to warn about usages that will become unsupported in 3.0." So I think it is a good idea to migrate to 2.6 first (and perhaps then, use that feature of a "-3" swithch to get an idea of what code in Sage needs to be rewritten). Also I think it is important to wait in order that all the sage components support Python 3.0 first. Pablo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
