[Python-Dev] Replacement for print in Python 3.0 (original) (raw)
Delaney, Timothy (Tim) tdelaney at avaya.com
Wed Sep 7 00:37:26 CEST 2005
- Previous message: [Python-Dev] Python core documentation
- Next message: [Python-Dev] string formatting options and removing basestring.__mod__ (WAS: Replacement for print in Python 3.0)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Chermside wrote:
We could satisfy both people if in Python 2.x we introduced a built-in function named "print30" (for Python 3.0) with the intended new behavior. People could start coding now using the "print30" builtin. When Python 3.0 was released, 'print' would no longer be a keyword, and both 'print' and 'print30' would be built-ins that both refered to the same function.
-1000
It's ugly, and it doesn't help the transition whatsoever IMO. We definitely don't want a print30 function hanging around in Python 3.0 for backwards compatibility with the miniscule number of people who used it in Python 2.x.
The simplest solution is (as already stated)::
from __future__ import __print_function__Tim Delaney
- Previous message: [Python-Dev] Python core documentation
- Next message: [Python-Dev] string formatting options and removing basestring.__mod__ (WAS: Replacement for print in Python 3.0)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]