A RetroSearch Logo

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

Search Query:

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

[Python-Dev] transform() and untransform() methods, and the codec registry

[Python-Dev] transform() and untransform() methods, and the codec registryRaymond Hettinger raymond.hettinger at gmail.com
Mon Dec 6 20:06:56 CET 2010
On Dec 3, 2010, at 10:05 AM, Guido van Rossum wrote:
> Regardless of what I or others may have said before, I am not
> currently a fan of adding transform() to either str or bytes.


Just to clarify, is your preference to go back to the Python 2.x way 
and use encode()/decode() for both unicode encodings and other
other transformations (uu, zlib, bz2, quopri, etc)?

FWIW, transform()/untransform() are already in the 3.2 beta.
Do you want them taken out?   If so, do you want the codecs
made accessible with encode/decode or have them continue
to be inaccessible in 3.x?


Raymond

More information about the Python-Dev mailing list

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