On Wednesday, April 3, 2019 at 10:11:19 AM UTC-7, kcrisman wrote: > > > > On Tuesday, April 2, 2019 at 6:03:23 PM UTC-4, Dima Pasechnik wrote: >> >> On Tue, Apr 2, 2019 at 10:47 PM <dsejas.m...@gmail.com <javascript:>> >> wrote: >> > >> > Hello, Sage community. >> > With the upcoming migration of Sage from Python2 to Python3, I was >> wondering if the "print" statement will be changed to the new "print" >> function. In any case, will there be backwards compatibility with the >> current behavior? >> >> As you can see in the current sage sources, there are no print statements >> left, >> only print functions. >> >> the trick with Python 2 is to do >> >> from __future__ import print_function >> >> to get this compatibility >> > > I think the post was asking for the reverse compatibility, though. > Presumably this would be possible (but perhaps not advisable) with adding > something to the preparser. I would be okay with a preparser addition that > would look for this and say something like "print blah should now be > print(blah)" but raise an error. >
Some of this has been discussed at https://trac.sagemath.org/ticket/23674. That ticket should be revived, especially if there is any consensus about how to handle this. I like the idea of deprecating statements like "print x" ASAP. -- John -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
