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 r.david.murray
Recipients georg.brandl, inkerman, pitrou, r.david.murray, roippi, serhiy.storchaka
Date 2014-11-13.18:42:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415904128.84.0.327023929585.issue22687@psf.upfronthosting.co.za>
In-reply-to
Content
What I usually do in cases like this is to add the tests but mark them with comments saying that the tests test current behavior but are not testing parts of the (currently defined) API.  That way you know if a change changes behavior and then can decide if that is a problem or not, as opposed to inadvertently changing behavior and only finding out when the bug reports roll in :)

But yeah, defining the rules textwrap should follow is a different issue than the performance issue.
History
Date User Action Args
2014-11-13 18:42:08r.david.murraysetrecipients: + r.david.murray, georg.brandl, pitrou, serhiy.storchaka, roippi, inkerman
2014-11-13 18:42:08r.david.murraysetmessageid: <1415904128.84.0.327023929585.issue22687@psf.upfronthosting.co.za>
2014-11-13 18:42:08r.david.murraylinkissue22687 messages
2014-11-13 18:42:08r.david.murraycreate