Re: [sage-devel] print to python3

On Tue, May 24, 2016 at 1:56 PM, William Stein wrote: > We need a real strategy for migrating users to Python3, and definitely > not some half-way thing that deals only with the print statement. > Just lurking here, but that was precisely the thought that came to my mind. For

Re: [sage-devel] print to python3

Fernando, Thanks for your post! The assumption in this whole thread is that Sage supports either python2 or python3, and not both. Thanks for questioning this assumption and pointing out that "all the major scientific python libraries are py2/3 compatible".This reminds me again of this post

Re: [sage-devel] print to python3

On Tue, 24 May 2016, Nils Bruin wrote: For people who use notebook servers, one could easily run a jupyter notebook server that supports both a sage-7.* and a sage-8.0 kernel, providing a platform to migrate from one to the other with relative ease (this will probably be a little harder with

Re: [sage-devel] print to python3

On 2016-05-24 20:20, Nils Bruin wrote: figuring out where the parentheses go for other uses of print is going to be tricky. I'm not sure something that is just regex based will do the job. It doesn't have to be perfect. It's already easily possible to fool the preparser with strange

Re: [sage-devel] print to python3

On 2016-05-24 20:27, Johan S. R. Nielsen wrote: 2) After that, for X years, issue a deprecation warning *every time* "print a" is used. As I said before, I don't like this part. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

Re: [sage-devel] print to python3

On Tuesday, May 24, 2016 at 1:56:56 PM UTC-7, William wrote: > > Hi, > > I've been thinking more, and I'm really disturbed by this piecemeal > approach to getting Python 3, as least as far as it impacts *users* > (for developers it is great). > [...] > For example, I'm finally using print as a

[sage-devel] Re: print to python3

Hello everybody, we are now almost ready to try to use the Python 3 print() function everywhere in Sage: doctests, command-line, notebook. This big switch is the aim of ticket http://trac.sagemath.org/ticket/20668. It still has to wait for an update of sagenb and for the next beta. This is an

Re: [sage-devel] Re: print to python3

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

Re: [sage-devel] Re: print to python3

On 2016-05-24 14:06, John Cremona wrote: in code (*.py) files. For .py code files, there is not really an issue since those can just do from __future__ import ... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

Re: [sage-devel] Re: print to python3

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 > wrote: > >> On 2016-05-24 14:06, John Cremona wrote: > >>> > >>> Would it be possible for > >>> > >>> sage: a=3

Re: [sage-devel] Re: print to python3

On 24 May 2016 at 13:17, Jeroen Demeyer 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

Re: [sage-devel] Re: print to python3

On Tue, 24 May 2016, John Cremona wrote: 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.

Re: [sage-devel] Re: print to python3

On 24 May 2016 at 12:33, Frédéric Chapoton wrote: > Hello everybody, > > we are now almost ready to try to use the Python 3 print() function > everywhere in Sage: doctests, command-line, notebook. > This big switch is the aim of ticket http://trac.sagemath.org/ticket/20668.

Re: [sage-devel] Re: print to python3

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. If you want that to continue working, it's better to not switch to Python 3 style printing. It's kind of silly to change

Re: [sage-devel] Re: print to python3

On 24/05/16 07:48, John Cremona wrote: On 24 May 2016 at 13:17, Jeroen Demeyer 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

Re: [sage-devel] Re: print to python3

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,

Re: [sage-devel] print to python3

On Tuesday, May 24, 2016 at 10:21:34 AM UTC-7, William 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.

Re: [sage-devel] print to python3

On Tue, May 24, 2016 at 11:20 AM, Nils Bruin wrote: > On Tuesday, May 24, 2016 at 10:21:34 AM UTC-7, William 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

[sage-devel] print to python3

> 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

Re: [sage-devel] print to python3

On Tue, May 24, 2016 at 11:27 AM, Johan S. R. Nielsen 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

Re: [sage-devel] print to python3

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

Re: [sage-devel] print to python3

On Tue, 24 May 2016, Johan S. R. Nielsen wrote: 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. 0) For a

Re: [sage-devel] print to python3

Hi, I've been thinking more, and I'm really disturbed by this piecemeal approach to getting Python 3, as least as far as it impacts *users* (for developers it is great). As mentioned before, I've been writing tons of code using Python 3 for the last two weeks. There are *many* subtle ways in

Re: [sage-devel] print to python3

I agree with Johann's proposal, with X=1 year as William proposed. The doc will very soon already have print() everywhere. I have contacted at least one author of the French book. They want to make a revised edition and an English traduction, and they will use print(). Who is volunteering to

Re: [sage-devel] print to python3

On Tue, 24 May 2016, Frédéric Chapoton wrote: I agree with Johann's proposal, with X=1 year  as William proposed. The doc will very soon already have print() everywhere. In beta, yes. But 7.2 was just released, so it will take time for 7.3 to be out. I have contacted at least one author