"Michael Urman" <[EMAIL PROTECTED]> wrote: > On 12/7/06, Fredrik Lundh <[EMAIL PROTECTED]> 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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com