RetroSearch Browse

Thu Aug 12 03:56:42 CEST 2004 · https://mail.python.org/pipermail/python-dev/2004-August/047665.html

Michael Chermside <mcherm at mcherm.com>:

> 'basestring' is a completely different issue -- there will always be
> a need for both unicode and 8-bit-strings as separate types.

I'm not so sure about that. There will certainly be a need for
something holding an arbitrary sequence of bytes, but it's not clear
that it needs to be called anything with 'string' in it.

I can enivisage a future in which 'string' means unicode string, and
byte sequences are called something else entirely, such as
'bytevector' or 'bytearray' (or maybe just 'array' :-).

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
greg at cosc.canterbury.ac.nz	   +--------------------------------------+

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

Showing content from https://mail.python.org/pipermail/python-dev/2004-August/047665.html below:

[Python-Dev] Unifying Long Integers and Integers: baseint