[Python-Dev] Replacement for print in Python 3.0
Bill Janssen
janssen at parc.com
Sun Sep 4 00:40:19 CEST 2005
More information about the Python-Dev mailing list
Sun Sep 4 00:40:19 CEST 2005
- Previous message: [Python-Dev] Replacement for print in Python 3.0
- Next message: [Python-Dev] Hacking print (was: Replacement for print in Python 3.0)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> I do hate having to write two parentheses -- it's more than the extra > keystrokes. It's that I have to use two shifted characters and I have > to be sure to close the construct, which can be a PITA when the start of > the function call is separated from the end by many lines. > What I found is that while this can be a real annoyance for some code, > there are some beneficial trade-offs that make this palatable... > So for permanent code, I think it's a decent trade-off. We lose > something but we gain something. I'll mourn the syntax highlighting > loss (or end up hacking python-mode) but oh well. Wouldn't it make sense then to replace the "print" statement with a "printf" statement? Then you'd get the formatting, and wouldn't have to type the parentheses. I don't see an argument for moving to a function; indeed, there's an argument against. What you want is a fancier print. Bill
- Previous message: [Python-Dev] Replacement for print in Python 3.0
- Next message: [Python-Dev] Hacking print (was: Replacement for print in Python 3.0)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list