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 chris.jerdonek
Recipients chris.jerdonek, ethan.furman, gward, jcea, pitrou, twouters
Date 2012-08-04.00:32:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> As far as these changes don't fix obvious bugs, no, they shouldn't.
People certainly rely on the current behaviour, and they will start
getting extraneous newlines if you change it (because they will call

That line of reasoning is acceptable to me.  And I said from the beginning that I'm open to resolving this issue via changes to the documentation.

But I feel this criterion was not applied to issue 1859.  wrap()'s behavior on newlines is broken to the point that multi-paragraph input is acknowledged as not working.  Additionally, because of that the keyword argument replace_whitespace has no clear use case.  That seems like an obvious bug to me.
Date User Action Args
2012-08-04 00:32:03chris.jerdoneksetrecipients: + chris.jerdonek, twouters, gward, jcea, pitrou, ethan.furman
2012-08-04 00:32:03chris.jerdoneksetmessageid: <>
2012-08-04 00:32:03chris.jerdoneklinkissue15510 messages
2012-08-04 00:32:02chris.jerdonekcreate