On Thursday, 21 March 2019 21:47:25 UTC-6, William Stein wrote: > > What if > > print "blah" > > in Sage started showing a deprecation warning as of the next release? > > Is there really much else besides print statements that people are > likely to write in the sage cell server that is Python2 only? I > can't think of anything else at all off the top of my head... I > realize that much of the Python2-->Python3 switch involves handling of > strings/unicode/bytes and change in the way rich comparison works. > However, I bet neither of those big landmines in the sage library are > used in typical applications of the sage cell server. > > -- William > That is also a very valid point and I think it is wise to do something in Sage itself to cover all interfaces and use cases.
Note that issues with print are somewhat similar to issues with "html(...)" which a few years back stopped displaying stuff by itself requiring "show(html(...))" or something similar. There were some complaints and problems with this, but we survived! -- You received this message because you are subscribed to the Google Groups "sage-cell" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cell/d153fe1b-3f71-4efa-a102-131ce2ea1152%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
