On 6/30/10 5:52 AM, Lie Ryan wrote:
On 06/27/10 11:24, Steven D'Aprano wrote:
Producing print function takes a little bit more effort than producing a
print statement.
(1) The main use-cases for print are quick (and usually dirty) scripts,
interactive use, and as a debugging aid.
That is precisely how the quick-and-dirty syntax of print statement can
be justified. While debugging, you'll need to be able to quickly add and
delete prints here and there, and the extra parens can quickly become
irritating.
I want to stamp a [Citation Needed] claim on that :)
Considering all the other things you're likely to do during 'quick and
dirty' debugging, an extra set of parens seems terribly unlikely to
really be any kind of issue. And if you have an editor worth its salt,
it'll take care of a lot of that anyways.
That justification sounds like its based on a
mountain-out-of-a-mole-hill complaint: print() is really not that
significantly more difficult then the print statement. This isn't Ruby
or another language which has determined () is an onerous requirement
for executing something.
--
... Stephen Hansen
... Also: Ixokai
... Mail: me+list/python (AT) ixokai (DOT) io
... Blog: http://meh.ixokai.io/
--
http://mail.python.org/mailman/listinfo/python-list
