Re: from __future__ import print

2008-04-20 Thread Roy Smith
"Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > You are aware that it is only one character more to type? I'm not arguing for print vs. print(), but I do want to comment on the "character count" argument. I'm a pretty good typist, the result of having been forced in junior high school (in the

Re: from __future__ import print

2008-04-20 Thread Diez B. Roggisch
Lie schrieb: > On Apr 13, 7:23 pm, Roy Smith <[EMAIL PROTECTED]> wrote: >> In article >> <[EMAIL PROTECTED]>, >> >> Lie <[EMAIL PROTECTED]> wrote: >>> I wish py3k >>> would make it an option whether to treat print as statement or >>> function though. >> Arrrggh! No, don't even go there. If

Re: from __future__ import print

2008-04-20 Thread Lie
On Apr 13, 7:23 pm, Roy Smith <[EMAIL PROTECTED]> wrote: > In article > <[EMAIL PROTECTED]>, > > Lie <[EMAIL PROTECTED]> wrote: > > I wish py3k > > would make it an option whether to treat print as statement or > > function though. > > Arrrggh! No, don't even go there. If you want optional

Re: from __future__ import print

2008-04-13 Thread Roy Smith
In article <[EMAIL PROTECTED]>, Lie <[EMAIL PROTECTED]> wrote: > I wish py3k > would make it an option whether to treat print as statement or > function though. Arrrggh! No, don't even go there. If you want optional parens, use Perl :-) -- http://mail.python.org/mailman/listinfo/python

Re: from __future__ import print

2008-04-13 Thread Lie
On Apr 11, 7:26 pm, Bruno Desthuilliers wrote: > [EMAIL PROTECTED] a écrit : > > > Am I the only one that thinks this would be useful? :) > > > I'd really like to be able to use python 3.0's print statement in > > 2.x. > > > FWIW, the whole point is that in 3.0, print stop being a statement to >

Re: from __future__ import print

2008-04-12 Thread [EMAIL PROTECTED]
On Apr 10, 3:06 pm, "Andrii V. Mishkovskyi" <[EMAIL PROTECTED]> wrote: > 2008/4/10, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > > Am I the only one that thinks this would be useful? :) > > > I'd really like to be able to use python 3.0'sprintstatement in > > 2.x. Is this at least being considere

Re: from __future__ import print

2008-04-11 Thread Bruno Desthuilliers
[EMAIL PROTECTED] a écrit : > Am I the only one that thinks this would be useful? :) > > I'd really like to be able to use python 3.0's print statement in > 2.x. FWIW, the whole point is that in 3.0, print stop being a statement to become a function... -- http://mail.python.org/mailman/listi

Re: from __future__ import print

2008-04-10 Thread Andrii V. Mishkovskyi
2008/4/10, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > Am I the only one that thinks this would be useful? :) > > I'd really like to be able to use python 3.0's print statement in > 2.x. Is this at least being considered as an option for 2.6? It > seems like it would be helpful with transitionin

from __future__ import print

2008-04-10 Thread [EMAIL PROTECTED]
Am I the only one that thinks this would be useful? :) I'd really like to be able to use python 3.0's print statement in 2.x. Is this at least being considered as an option for 2.6? It seems like it would be helpful with transitioning. -- http://mail.python.org/mailman/listinfo/python-list