I've heard several times that print being a function (3.x) is better than it being a statement (2.x). But why?
I was a fan of it being a statement mainly because it allowed me to type two less characters (ie, the parentheses).
I'd be interested to see some situations where the print statement just doesn't cut it, and a function is superior.
Python print() Function The print() function prints the specified message to the screen, or other standard output device. The message can be a string, or any other object, the object will be converted into a string before written to the screen.
This is because they both have a function defined called print that takes in a string argument and prints it. Python2 also allowed you to make a statement to print to standard out without calling a function.
print(' ') will print a space character and a newline; while print('') (or print() ) will only print the newline. It doesn't take away anything. Thank you very much!
Rationale
The print statement has long appeared on lists of dubious language features that are to be removed in Python 3000, such as Guido's "Python Regrets" presentation [1]. As such, the objective of this PEP is not new, though it might become much disputed among Python developers.
The following arguments for a print() function are distilled from a python-3000 message by Guido himself [2]:
- print is the only application-level functionality that has a statement dedicated to it. Within Python's world, syntax is generally used as a last resort, when something can't be done without help from the compiler. Print doesn't qualify for such an exception.
- At some point in application development one quite often feels the need to replace print output by something more sophisticated, like logging calls or calls into some other I/O library. With a print() function, this is a straightforward string replacement, today it is a mess adding all those parentheses and possibly converting >>stream style syntax.
- Having special syntax for print puts up a much larger barrier for evolution, e.g. a hypothetical new printf() function is not too far fetched when it will coexist with a print() function.
- There's no easy way to convert print statements into another call if one needs a different separator, not spaces, or none at all. Also, there's no easy way at all to conveniently print objects with some other separator than a space.
- If print() is a function, it would be much easier to replace it within one module (just
def print(*args):...
) or even throughout a program (e.g. by putting a different function in__builtin__.print
). As it is, one can do this by writing a class with a write() method and assigning that to sys.stdout – that's not bad, but definitely a much larger conceptual leap, and it works at a different level than print.— PEP 3105 – Make print a function
Everything from Jochen's answer and Sven's answer, plus:
You can use print()
it in places where you can't use print
, such as:
[print(x) for x in range(10)]
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With