On 07/01/10 01:42, Michele Simionato wrote: > On Jun 30, 2:52 pm, Lie Ryan <lie.1...@gmail.com> 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. > > Actually when debugging I use pdb which uses "p" (no parens) for > printing, so having > print or print() would not make any difference for me.
You mean I have to start a full-blown debugger to figure out the value of a variable? No thanks, debugger has its use for stepping through program, but not when printing values is sufficient. -- http://mail.python.org/mailman/listinfo/python-list
