[Python-Dev] The fate of transform() and untransform() methods

Michael Foord fuzzyman at voidspace.org.uk
Thu Dec 9 16:13:36 CET 2010

On 09/12/2010 15:03, M.-A. Lemburg wrote:
> Alexander Belopolsky wrote:
>> On Fri, Dec 3, 2010 at 1:05 PM, Guido van Rossum<guido at python.org>  wrote:
>>> On Fri, Dec 3, 2010 at 9:58 AM, R. David Murray<rdmurray at bitdance.com>  wrote:
>> ..
>>>> I believe MAL's thought was that the addition of these methods had
>>>> been approved pre-moratorium, but I don't know if that is a
>>>> sufficient argument or not.
>>> It is not.
>>> The moratorium is intended to freeze the state of the language as
>>> implemented, not whatever was discussed and approved but didn't get
>>> implemented (that'd be a hole big enough to drive a truck through, as
>>> the saying goes :-).
>>> Regardless of what I or others may have said before, I am not
>>> currently a fan of adding transform() to either str or bytes.
>> I would like to restart the discussion under a separate subject
>> because the original thread [1] went off the specific topic of the six
>> new methods (2 methods x 3 types) added to builtins shortly before 3.2
>> beta was released. [2]  The ticket that introduced the change is
>> currently closed [3] even though the last message suggests that at
>> least part of the change needs to be reverted.
> That's for Guido to decide.

Well, Guido *already* said no to transform / untransform in the previous 


> The moratorium, if at all, would only cover the new methods,
> not the other changes (readding the codecs and fixing the
> codecs.py module to work with bytes as well as Unicode), all
> of which were already discussed at length in several previous
> discussion, on tickets and on python-dev.
> I don't see much point in going through the same discussions
> over and over again. Fortunately, I'm on vacation next week,
> so don't have to go through all this again ;-)
> Cheers,



READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.

More information about the Python-Dev mailing list