Terry Reedy wrote:
Would you prefer re_transform, which is English?
Fiddling with the name of the antonym doesn't help.
The direction of "untransform" or whatever it's
called is only as clear as the direction of
"transform".
--
Greg
___
Python-3000
On 16 May 2008, at 08:31, Greg Ewing wrote:
Fiddling with the name of the antonym doesn't help.
How about adding a direction indicator?
gzipped = plaintext.transformto("gzip")
plaintext = gzipped.transformfrom("gzip")
Mark
___
Python-3000
Fiddling with the name of the antonym doesn't help.
The direction of "untransform" or whatever it's
called is only as clear as the direction of
"transform".
How about making the transformation parameter more descriptive?
gzipped = plaintext.transform(plaintext_to_gzip)
plaintext = gzipped
Greg Ewing wrote:
There's nothing wrong with that, but what it doesn't
answer is why it's not sufficient just to do things
like
from gzip import gzip_codec
stream2 = BytesTransform(gzip_codec, stream1)
i.e. why there has to be a special kind of namespace
for codecs.
Selecting an encoding is t
I wrote:
...and it doesn't have to be reflexive if that...
Umm, that should have said 'have an inverse', which is different than
reflexive or symmetric. I get a little lost on 'surjective' and
'injective', having been taught the terms 'onto' and 'one-to-one'. But
I digress.
For wrapping
Joel Bender writes:
> > Fiddling with the name of the antonym doesn't help.
> > The direction of "untransform" or whatever it's
> > called is only as clear as the direction of
> > "transform".
>
> How about making the transformation parameter more descriptive?
>
> gzipped = plaintext
