On 07/01/10 01:30, Stephen Hansen wrote: > 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 :)
That's based on my own anecdotal experience. > 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. You want to focus on doing these "other things you're likely to do" instead of having to do the function call keyboard dance. > 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. indeed it isn't a major irritant; but it *is* irritating. -- http://mail.python.org/mailman/listinfo/python-list
