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 vstinner
Recipients Arfrever, ezio.melotti, lemburg, martin.panter, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, sjt, steven.daprano, vstinner
Date 2015-09-27.08:55:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Hum, I suggest to put these functions in a package on PyPI, or recipes on a
website like stackoverfkow., and close the issue.

I'm still not convinced that these functions are useful . Usually we take a
function from an existing project used in applications to put it in the
stdlib. Here the use case still looks artifical. For example which
application requires to escape non-BMP character? How does it handle them

Threre are too many ways to handle surrogate characters. The common ways to
show undecodable bytes are not supported by functions proposed by Serhiy.
Example: %80 on Mac OS X. Gnome uses something else.

It was said that one reason to add new functions is performance. I'm not
convinced neither that such function is the bottleneck on any application.

I prefer to wait until users experiment with their own implementation and
see if a common function can be extracted from this to put it in the stdlib.
Date User Action Args
2015-09-27 08:55:47vstinnersetrecipients: + vstinner, lemburg, ncoghlan, pitrou, ezio.melotti, Arfrever, steven.daprano, r.david.murray, sjt, martin.panter, serhiy.storchaka
2015-09-27 08:55:47vstinnerlinkissue18814 messages
2015-09-27 08:55:46vstinnercreate