On Sun, Jul 31, 2011 at 10:59 PM, François <[email protected]> wrote: > For those interested Jason Grout has already filled a ticket to upgrade to > ipython-0.10.2 (trac #11460) with a comment that Fernando told him that > it would be better to skip 0.11.
I should qualify that comment with a bit of context: there's a TON of changes in 0.11, and the internal customization APIs are all very different. This means a lot of stuff that Sage does won't work out of the box with 0.11. However, we will need some help from the Sage team to find out areas where we may have inadvertently dropped a feature or removed an entry point without putting in a replacement in the new APIs. Since Sage makes more intense use of IPython than most other projects, there are things we'll only find out about once Sage tries to update. All this means that while 0.11 is not likely to be an easy update for Sage, simply waiting will not work either. The best approach would be for someone to give 0.11 a try and let us know what breaks by opening issues in our tracker (https://github.com/ipython/ipython/issues) and asking on our -dev mailing list (http://mail.scipy.org/mailman/listinfo/ipython-dev). That way, hopefully they will get resolved during the 0.12 cycle and then when 0.12 does come out, it will be realistic for Sage to actually upgrade without troubles. Cheers, f -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
