On Tue, May 24, 2016 at 11:27 AM, Johan S. R. Nielsen <santaph...@gmail.com> wrote: >> Breaking "print a" will cause a truly epic level of pain to our users for >> no real gain... So much so that probably no matter what is decided here I >> would fork sage to add handling this to the pre-processor for sage on SMC. >> I'm here from endless users (eg each year at the sage booth) about minor >> deprecations that piss them off. This print thing will be horrible. >> Truly horrible. >> ... >> (Personally i really like Python3 and the new print function. However, I >> (and you) are not the only user of sage.) > > I also think that this will annoy a lot of users. On the other hand, > Python 3 is already old, and the transition has to come at some point. > In 2020, at the latest we shouldn't be supporting Python 2 at all. > > Perhaps a tolerable amount of pain would be to do the deprecation in > several steps: > > 1) For year, issue only a deprecation *the first time* "print a" is used > in a session. > 2) After that, for X years, issue a deprecation warning *every time* > "print a" is used. > 3) After that, remove support for "print a" completely. > > Best, > Johan
I support your proposal above, with X=1. I don't want to have the print statement forever. -- William > > > > William Stein writes: > >> Breaking "print a" will cause a truly epic level of pain to our users for >> no real gain... So much so that probably no matter what is decided here I >> would fork sage to add handling this to the pre-processor for sage on SMC. >> I'm here from endless users (eg each year at the sage booth) about minor >> deprecations that piss them off. This print thing will be horrible. >> Truly horrible. >> >> I programmed in python3 many of my waking hours for the last 2 weeks and >> even last night I was still making mistakes with print. I'm absolutely >> certain users will have similar trouble, both adapting their own code and >> in changing. It's just psychology. >> >> (Personally i really like Python3 and the new print function. However, I >> (and you) are not the only user of sage.) >> >> William >> >> On Tuesday, May 24, 2016, John Cremona <john.crem...@gmail.com> wrote: >> >>> We seem to be stuck. The possibilities are >>> >>> (1) make "print a" just stop working at some point (maybe not yet) >>> (2) as (1) but with a deprecation warning >>> (3) continue to support "print a" for ever. >>> >>> All three have had some negative votes! >>> >>> Jeroen, I also do not like "endless" deprecation warnings, but if it >>> was limited to one per session (assuming that is technically possible) >>> it would not be so bad? >>> >>> John >>> >>> On 24 May 2016 at 14:35, Jeroen Demeyer <jdeme...@cage.ugent.be >>> <javascript:;>> wrote: >>> > On 2016-05-24 15:27, Travis Scrimshaw wrote: >>> >> >>> >> every time, not just the first >>> > >>> > >>> > -1. We should not annoy our users with endless deprecation warnings. >>> > >>> > >>> > -- >>> > 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 <javascript:;>. >>> > To post to this group, send email to sage-devel@googlegroups.com >>> <javascript:;>. >>> > Visit this group at https://groups.google.com/group/sage-devel. >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> 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 <javascript:;>. >>> To post to this group, send email to sage-devel@googlegroups.com >>> <javascript:;>. >>> Visit this group at https://groups.google.com/group/sage-devel. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> Sent from my massive iPhone 6 plus. > > > -- > > -- > 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. -- William (http://wstein.org) -- 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.
