[Python-3000] PEP 3138- String representation in Python 3000 (original) (raw)
Guido van Rossum guido at python.org
Wed May 14 23:42:30 CEST 2008
- Previous message: [Python-3000] PEP 3138- String representation in Python 3000
- Next message: [Python-3000] PEP 3138- String representation in Python 3000
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 14, 2008 at 2:39 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
M.-A. Lemburg wrote:
On 2008-05-14 18:33, Georg Brandl wrote:
M.-A. Lemburg schrieb:
Fine, so we need new methods for PyUnicode and PyString objects which allow encoding and decoding using the same type (and enforce the return types). Any suggestions ? How about these: str.strencode() -> str str.strdecode() -> str bytes.bytesencode() -> bytes bytes.bytesdecode() -> bytes Cool, a naming contest :) What about transform/untransform? Not bad :-) Here's a version without underscores: str.encodestr() -> str str.decodestr() -> str bytes.encodebytes() -> bytes bytes.decodebytes() -> bytes A couple more possibilities (Guido is probably going to have to choose a colour for this bikeshed somewhere along the line...): mystr.recodeto('unicode-escaped') mystr.recodefrom('unicode-escaped') mybytes.recodeto('hex') mybytes.recodefrom('hex')
Nah. I'm still in favor of [un]transform. Let's just stick to that.
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-3000] PEP 3138- String representation in Python 3000
- Next message: [Python-3000] PEP 3138- String representation in Python 3000
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]