> >> 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! >
Yes, agreed here. By far the greatest Py3 incompatibility will be print - though that will be a lot bigger of an issue than the pretty_print(html(...)) one. I would certainly be in support of a deprecation of the print statement within Sage, if feasible, once we really have Sage-the-distribution working fully with Py3 and the transition is only a matter of time. We'd probably want to have various pinned posts, FAQ updates - and so forth. Timing for the true switchover (i.e. no more Py2 in Sage cell)? I would recommend it were over the Northern hemisphere summer. Probably June 1 is a good date - I'd say 2020, but I know others are itching for earlier. For people with high teaching loads, changing a lot of stuff over winter break is not feasible. I know not every country has that academic schedule, many people in the States even teach summer courses ... but if there had to be a time, that probably should be it. For Sage itself, ironically, people can just not upgrade. Timing is part of it, but since we still get lots of requests for support of even 5.x and 6.x that won't be as bad. William, would Sage pre-Py3 kernels be available on CoCalc for a while perhaps after a Sage switch? Just curious. Could be a useful use of an email blast to all your customers ... All of this is train of thought, so if there are dumb ideas, no worries, just trying to unload all of them at the end of the week :) Thanks for always being so on top of this, Andrey. -- 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/b3fb8e9a-dbf9-4f5a-a686-f02031d80aa5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
