> After discussing issue15510, I think this should probably be left as-is, or be implemented in a separate function so as to avoid breaking compatibility.

Note that this issue can be addressed without affecting backwards compatibility in the documented supported cases.  textwrap.wrap()'s documentation says that it only supports single paragraph input and even warns against "strange output" otherwise.

Also, as Mark pointed out above, what use case does replace_whitespace=False have if this issue is not addressed?

http://bugs.python.org/issue1859#msg96064

Addressing this issue would give that argument meaning (for multi-paragraph input).

Finally, just to be clear, I marked issue 15510 as a dependency in the sense that I felt it should be decided before addressing this issue -- not that the issue needed to be addressed in the affirmative.