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

Showing content from https://mail.python.org/pipermail/python-dev/2001-October/017889.html below:

[Python-Dev] Bug or feature? Unicode vs t#

• Previous message: [Python-Dev] Bug or feature? Unicode vs t#
• Next message: [Python-Dev] Bug or feature? Unicode vs t#
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "PP" == Paul Prescod <paul@ActiveState.com> writes:

  PP> Translating the data before handing it to the user violates the
  PP> "raw"-ness of the byte-oriented format and the principle about
  PP> not needing to copy it. It behaves quite differently than other
  PP> implementations of getcharbuffer.

As far as I can tell, all other implementations of getcharbuffer are
exact duplicates of getreadbuffer.  If the Unicode object doesn't have
an appropriate implementation of getcharbuffer, one wonders why the
method exists at all:  In every case it would be redundant or
incorrect. 

Jeremy

• Previous message: [Python-Dev] Bug or feature? Unicode vs t#
• Next message: [Python-Dev] Bug or feature? Unicode vs t#
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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