Richard Katz added the comment:

"What's wrong with

py> for x in 1,2,3:print(x,end=" ")"
-------------------------
I'd like to suggest (for those of us just now focusing on Python 3.0) replacing 
the last 3 bullet points of the paragraph "Common Stumbling Blocks?" 
http://docs.python.org/dev/3.0/whatsnew/3.0.html

With the following simple reference:

"The print statement has been REMOVED and is replaced by a print() function. 
SEE PEP 3105." 

Rather than burying 3105 in the middle of "other language changes."  That would 
do a lot to clear it up.  

A) Especially I'd like to suggest getting rid of the quite cryptic: "You’ll be 
finding yourself typing print x a lot in interactive mode." I had no idea that 
was a *warning message - meaning "it won't work..." And 

B) The rather misleading - "Also, print and print (x, y)  behave differently 
without warning:"

They certainly do...   But not in the way explained. "print" now displays 
"<built-in function print>" since it's a function...    What they probably 
meant was print()? 

Where would I suggest (or make) these changes to What's New? Is there a Doc 
Wiki?

Thanks!

Regards,

Rich

-----Original Message-----
>From: "=?utf-8?q?Martin_v._L=C3=B6wis?=" <[EMAIL PROTECTED]>
>Sent: Sep 4, 2007 5:31 PM
>To: [EMAIL PROTECTED]
>Subject: [issue1101] Is there just no PRINT statement any more? Or it just 
>doesn't work.
>
>
>Martin v. Löwis added the comment:
>
>What's wrong with
>
>py> for x in 1,2,3:print(x,end=" ")
>...
>1 2 3
>
>Closing as invalid.
>
>----------
>nosy: +loewis
>resolution:  -> invalid
>status: open -> closed
>
>__________________________________
>Tracker <[EMAIL PROTECTED]>
><http://bugs.python.org/issue1101>
>__________________________________

__________________________________
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1101>
__________________________________
_______________________________________________
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to