On Tuesday, May 24, 2016 at 7:55:49 AM UTC-5, vdelecroix wrote: > > On 24/05/16 07:48, John Cremona wrote: > > On 24 May 2016 at 13:17, Jeroen Demeyer <jdem...@cage.ugent.be > <javascript:>> wrote: > >> On 2016-05-24 14:06, John Cremona wrote: > >>> > >>> Would it be possible for > >>> > >>> sage: a=3 > >>> sage: print a > >>> > >>> to work on the command line, using the preparser? > >> > >> > >> That already works today. > > > > But would it still work after a total conversion of Sage to Python 3? > > > > Most Sage users do not care a fig about Python versions, but will care > > if after 10 years of being able to type "print a" they are suddenly > > forced into typing "(print(a)". Iwas thinking about this from a user > > perspective not a developer perspective. > > > > I agree with John. We should add a DeprecationWarning in the Sage > preparser right now for "print X, Y, Z" and make it such that "print(X, > Y, Z)" really behaves like Python 3. > > Nothing will change with .py files. But in the console, notebook and > .sage files users would be noticed. > > I also agree with John's suggestion as a *temporary* measure which warns users (every time, not just the first) that it will no longer be supported, which will include anyones .sage files too.
Also, I think the longer we delay on becoming Python3 compliant, the more we are losing in potential users and developers who are starting by learning Python3. Best, Travis -- 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.
