➜

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 methane
Recipients jonathaneunice, methane, r.david.murray
Date 2020-10-21.04:31:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1603254709.22.0.135379153082.issue30680@roundup.psfhosted.org>
In-reply-to
Content 
> Agreed. It makes great sense that textwrap started as highly ASCII-centric. But in the Python 3, Unicode-friendly era, ASCII-biased isn't where we should leave things.

It needs Unicode experts. If we support Unicode, we should implemente UAX #14.
http://www.unicode.org/reports/tr14/tr14-45.html

But I am not sure some core developer love textwrap and Unicode enough to implement it.
It can be implemented in 3rd party package before adding it in stdlib.

Then, is U+2014 really important to implement even though we can not implement UAX#14 in foreseeable future?
It doesn't make sense to me.
History
Date User Action Args
2020-10-21 04:31:49methanesetrecipients: + methane, r.david.murray, jonathaneunice
2020-10-21 04:31:49methanesetmessageid: <1603254709.22.0.135379153082.issue30680@roundup.psfhosted.org>
2020-10-21 04:31:49methanelinkissue30680 messages
2020-10-21 04:31:48methanecreate