On Monday, September 5, 2011 8:29:46 AM UTC+2, TimDaly wrote: > > I see Sage efforts to keep up with OS changes (e.g. Lion) and > package changes (e.g. Maxima) but I am unaware of any work > to keep up with Python. > There are plans to move to python 3.x somewhere in the future (at least I heard William and Robert Bradshaw discuss on the last bugdays when we should start thinking about switching). IIRC there hasn't been any work on changing to python3 because not all the things on wich sage depends work in python3 yet, once enough dependancy's work with python3 we will start switching. This will take a lot of effort tough.
> 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. > You can redefine any standard python function! Even to something witch is not a function. sage: len = "lol" sage: print len lol The only thing in python you cannot redefine are the keywords such as class, def, yield, return, etc. Even tough I'm pointing out that this is possible, this doesn't mean I'm a huge fan of doing this. And I don't think overwriting standard functions is the way to go when changing from python 2 to python 3. > As pointed out in the article, the longer this continues, the > harder, more expensive, and more disruptive the changes will be. > Yes, I think think the article was very usefull for making us more aware of the "dept" you create by not keeping up to date with upstream. > Tim Daly > > > -- 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
