GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [Python-Dev] Use of %c and Py_UNICODE
  • [Python-Dev] Use of %c and Py_UNICODE
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Use of %c and Py_UNICODE

[Python-Dev] Use of %c and Py_UNICODE

Tim Peters [email protected]
Sun, 17 Dec 2000 02:34:27 -0500

  • Previous message: [Python-Dev] Use of %c and Py_UNICODE
  • Next message: [Python-Dev] Use of %c and Py_UNICODE
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[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.




  • Previous message: [Python-Dev] Use of %c and Py_UNICODE
  • Next message: [Python-Dev] Use of %c and Py_UNICODE
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.