On Tue, May 26, 2015 at 1:01 PM, Volker Braun <[email protected]> wrote: > Personally, I'm fine with EOL for SageNB in 2020 together with Python 2.x. > IMHO we should focus our energy on having a superior alternative ready by > then.
+1 At some point hopefully soon Jupyter notebook should be a sufficient replacement to sagenb, due to excellent work of volker and others. It takes very much the same approach ui-wise as sagenb, and is just missing some graphics/other support. And under the hood the architecture is better. -- William > > > > On Tuesday, May 26, 2015 at 8:12:30 PM UTC+2, R. Andrew Ohana wrote: >> >> In the interest of reducing the work required for supporting Python 3, >> unless there is some champion out there who wants to do the hard work making >> sagenb work with Python 3, the sage notebook will not be joining the rest of >> sage with Python 3. >> >> So, with that said, is there anyone interested in porting (and >> maintaining) sagenb to python 3? >> >> -- >> Andrew > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
