Message 67688 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	evilnick
Recipients	evilnick, georg.brandl
Date	2008-06-04.10:30:55
SpamBayes Score	0.05904542
Marked as misclassified	No
Message-id	<1212575460.09.0.843945185699.issue3036@psf.upfronthosting.co.za>
In-reply-to

Content
In the whatsnew/3.0.html doc, the example for print is the wrong way around. Current version reads: * The :func:`print` function doesn't support the "softspace" feature of the old ``print`` statement. For example, in Python 2.x, ``print "A\n", "B"`` would write ``"A\nB\n"``; but in Python 3.0, ``print("A\n", "B")`` writes ``"A\n B\n"``. should read: * The :func:`print` function doesn't support the "softspace" feature of the old ``print`` statement. For example, in Python 2.x, ``print "A\n", "B"`` would write ``"A\n B\n"``; but in Python 3.0, ``print("A\n", "B")`` writes ``"A\nB\n"``.

In the whatsnew/3.0.html doc, the example for print is the wrong way
around. Current version reads:
* The :func:`print` function doesn't support the "softspace" feature of
    the old ``print`` statement.  For example, in Python 2.x,
    ``print "A\n", "B"`` would write ``"A\nB\n"``; but in Python 3.0,
    ``print("A\n", "B")`` writes ``"A\n B\n"``.

should read:
* The :func:`print` function doesn't support the "softspace" feature of
    the old ``print`` statement.  For example, in Python 2.x,
    ``print "A\n", "B"`` would write ``"A\n B\n"``; but in Python 3.0,
    ``print("A\n", "B")`` writes ``"A\nB\n"``.

History
Date	User	Action	Args
2008-06-04 10:31:01	evilnick	set	spambayes_score: 0.0590454 -> 0.05904542 recipients: + evilnick, georg.brandl
2008-06-04 10:31:01	evilnick	set	spambayes_score: 0.0590454 -> 0.0590454 messageid: <1212575460.09.0.843945185699.issue3036@psf.upfronthosting.co.za>
2008-06-04 10:30:58	evilnick	link	issue3036 messages
2008-06-04 10:30:57	evilnick	create