On Tue, May 26, 2015 at 11:53 AM, kcrisman <[email protected]> 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. >> >> > That would be really bad for backward incompatibility unless you mean > "Sage will support Python 2 and 3, but the notebook will only run under > 3". Even the likely-appearing SMC "personal edition" is really not the > same. > I mean that you will continue to be able to use sagenb under Python 2 (which Sage should support for a good long while), but unless someone ports sagenb to also work under Python 3, then you will not be able to use sagenb with sage on sagenb when you build sage with Python 3. > >> So, with that said, is there anyone interested in porting (and >> maintaining) sagenb to python 3? >> > > https://github.com/sagemath/sagenb/issues/343 > > I mean, how many Python 2-isms can there be in sagenb? (Other than > formatting, which we've already been trying to encourage people to switch > over - I don't know that there are a lot of print statements. Presumably > there are other things.) > > -- > 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. > -- 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.
