RetroSearch Browse

Thu Dec 7 17:58:20 CET 2006 · https://mail.python.org/pipermail/python-dev/2006-December/070268.html

"Michael Urman" <murman at gmail.com> wrote:
> On 12/7/06, Fredrik Lundh <fredrik at pythonware.com> wrote:
> > (and while you guys are waiting, I suggest you start a new thread where
> > you discuss some other inconsistency that would be easy to solve with
> > more code in the interpreter, like why "-", "/", and "**" doesn't work
> > for strings, lists don't have a "copy" method, sets and lists have
> > different API:s for adding things, we have hex() and oct() but no bin(),
> > str.translate and unicode.translate take different arguments, etc.  get
> > to work!)
> 
> Personally I'd love a way to get an unbound method that handles either
> str or unicode instances. Perhaps py3k's unicode realignment will
> effectively give me that.

Immutable byte strings won't exist in Py3k, and the mutable byte strings
(bytes) won't support very many, if any current string/unicode methods.

No bytes.replace, bytes.split, bytes.partition, etc.  So no, Py3k's
unicode change won't get you that.  All it will get you is that every
string you interact with; literals, file.read, etc., will all be text 
(equivalent to Python 2.x unicode).

 - Josiah

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

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

[Python-Dev] [NPERS] Re: a feature i'd like to see in python #2: indexing of match objects