> > > > 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. > > 2020 seems more than reasonable, for sure. My concerns are * That people can still (easily) use their worksheets regardless of which Sage they download/build *right now* (which suggests keeping sagenb Python3-compatible) * That there is a really good migration flow for sws -> whatever Jupyter will be, as with previous versions of sagenb migration * That Jupyter could be used as an in-house sagenb replacement for small-scale multi-user (which I hear is in the works) for those who would prefer this to trying to manage a local SMC installation But some of those questions may be naive.
-- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
