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 pitrou
Recipients chris.jerdonek, ethan.furman, gward, jcea, pitrou, twouters
Date 2012-08-03.22:45:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344033804.3377.30.camel@localhost.localdomain>
In-reply-to <>
> > That's because wrap() suppresses extra whitespace by default. 
> But the documentation for drop_whitespace clearly states that, after
> wrapping, "leading whitespace in the first line is always preserved,
> though."

Ok, then it's a bit fuzzy. That whitespace is as much trailing as
leading, after all :)

> I wouldn't say that it is "perfectly" logical.  String methods that
> drop characters from the beginning or end of a string return an empty
> string for empty text.
> >>> "   ".strip()
> ''

I'm not sure I see the relevance. strip() returns an empty string
because its return type is a string, what else could it return?

> > Furthermore, by "fixing" this, you may break existing software.
> Issue 1859 is an arguably larger change that will also break existing
> software, and that issue has been kept open.

Agreed. I'm gonna post on that issue too.
Date User Action Args
2012-08-03 22:45:56pitrousetrecipients: + pitrou, twouters, gward, jcea, chris.jerdonek, ethan.furman
2012-08-03 22:45:55pitroulinkissue15510 messages
2012-08-03 22:45:55pitroucreate