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-June/100545.html below:

[Python-Dev] Reintroduce or drop completly hex, bz2, rot13, ... codecs

[Python-Dev] Reintroduce or drop completly hex, bz2, rot13, ... codecsTerry Reedy tjreedy at udel.edu
Wed Jun 9 21:45:55 CEST 2010
On 6/9/2010 8:17 AM, Antoine Pitrou wrote:
> On Wed, 9 Jun 2010 13:57:05 +0200
> Dirkjan Ochtman<dirkjan at ochtman.nl>  wrote:
>> On Wed, Jun 9, 2010 at 13:40, Antoine Pitrou<solipsis at pitrou.net>  wrote:
>>> No, I don't think so. If I'm using hex "encoding", it's because I want
>>> to see a text representation of some arbitrary bytestring (in order to
>>> display it inside another piece of text, for example).
>>> In other words, the purpose of hex is precisely to give a textual
>>> display of non-textual data.
>>
>> Or I want to encode binary data in a non-binary-safe protocol, in
>> which case I probably want bytes.
>
> In this case you would probably choose a more space-efficient
> representation, such as base64 or base85.

Unless the receiver expects hex.

Please, hextext = str(somebytes.tranform('hex')) is quite easy and 
explicit and will work for any bytes to ascii-subset transform, not just 
'hex'.

Keep .transform and .untransform simple by *always* going to/from same 
type.

Terry Jan Reedy

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