A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-December/011073.html below:

[Python-Dev] Use of %c and Py_UNICODE

[Python-Dev] Use of %c and Py_UNICODE [Python-Dev] Use of %c and Py_UNICODETim Peters tim.one@home.com
Sun, 17 Dec 2000 02:34:27 -0500
[MAL]
> Why would you want to fix it ? Format characters will always
> be ASCII and thus 7-bit -- theres really no need to expand the
> set of possibilities beyond 8 bits ;-)

[AMK]
> This message is for characters that aren't format characters, which
> therefore includes all characters >127.

I'm with the wise man who suggested to drop the %c in this case and just
display the hex value.  Although it would be more readable to drop the %c if
and only if the bogus format character isn't printable 7-bit ASCII.  Which
is obvious, yes?  A new if/else isn't going to hurt anything.




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4