Is it strictly needed, no. However, it allows us to be compatible with Python3 and it helps prevent anyone in the future from adding code that is only works in Python2 wrt print statements. Furthermore, most of the docstrings can be made 2/3 compliant and don't need "fancy" print_function stuff. At some point (perhaps when we start 7.3.beta0?), we will change our interactive shell and doctesting framework to use the new print statements.
TL;DR, it doesn't hurt to add it. Best, Travis On Friday, May 6, 2016 at 8:32:33 AM UTC-5, Dima Pasechnik wrote: > > I already commented on one of these tickets that I do not understand why > `from __future__ import print_function` > is needed everywhere. > Indeed, most modules do not do nontrivial printing anywhere, except > perhaps docstrings > (and the latter are not affected by that import anyway). > > Dima > > On Tuesday, May 3, 2016 at 7:50:21 PM UTC+1, Frédéric Chapoton wrote: >> >> Hello, >> >> I am trying to move toward using the python3 syntax for print. >> >> This is done by small chunks, using a lot of tiny tickets, according the >> folders in sage, mostly. >> These tickets can be found at the bottom of >> >> http://trac.sagemath.org/query?status=!closed&component=python3 >> >> If some of you could find time to review one of those, that would help to >> advance the change. >> >> Many thanks to those that have already reviewed some of these. >> >> cheers, >> Frederic >> > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
