On Feb 6, 2014 10:16 AM, "Nils Bruin" <[email protected]> wrote: > > On Thursday, February 6, 2014 8:56:09 AM UTC-8, William wrote: >> >> When we do eventually switch to Python 3, I want to modify the preparse to allow >> use of print as statement still > > That may be challenging. How should the following be parsed (and which are syntax errors)? > > print (1,2,3) > print (1,2,3),"hi" > print (1,2,3,sep=";") > print (1,2,3,sep=";"),"hi"
They would all be not touched. I would lobby for only activating the preparser for print when the code would otherwise be syntactically invalid in python3. The preparser philosophy is that as much as possibly the preparser only transforms syntactically invalid code. The main point would be to address the large amount of user code in worksheets that looks like this: print M print "i =", i (At some point the preparser might emit a deprecation warning for use of print as a statement.) As Guido might say, the goal would not be full backward compatibility! > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/groups/opt_out. consentingly -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
