RetroSearch Browse

Wed Feb 22 21:28:52 CET 2006 · https://mail.python.org/pipermail/python-dev/2006-February/061723.html

Terry Reedy wrote:

> "Greg Ewing" <greg.ewing at canterbury.ac.nz> wrote in message 
>
>> Which is why I think that only *unicode* codings should be
>> available through the .encode and .decode interface. Or
>> alternatively there should be something more explicit like
>> .unicode_encode and .unicode_decode that is thus restricted.
> 
> I prefer the shorter names and using recode, for instance, for bytes to 
> bytes.

While I prefer constructors with an explicit encode argument, and use a 
recode() method for 'like to like' coding.  Then the whole encode/decode 
confusion goes away.

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-February/061723.html below:

[Python-Dev] bytes.from_hex()