Author flox
Recipients amaury.forgeotdarc, beazley, flox, vstinner
Date 2009-12-14.19:03:28
SpamBayes Score 1.40346e-06
Marked as misclassified No
Message-id <1260817410.57.0.0454124927922.issue4770@psf.upfronthosting.co.za>
In-reply-to
Content
I agree, we need consistency between all functions of this package.

I've run a small script to check what happens for all 16 functions of
the binascii package when they receive unicode input...

See attached script (and sample output).

IMHO 4 functions should be fixed to raise the same TypeError:
 - a2b_hex
 - a2b_qp
 - unhexlify
 - rledecode_hqx 

Documentation says that the functions in `binary` module « convert
between binary and various ASCII-encoded binary representations »
So... it's all binary.

Implicit encoding should not happen, never.
History
Date User Action Args
2009-12-14 19:03:30floxsetrecipients: + flox, beazley, amaury.forgeotdarc, vstinner
2009-12-14 19:03:30floxsetmessageid: <1260817410.57.0.0454124927922.issue4770@psf.upfronthosting.co.za>
2009-12-14 19:03:28floxlinkissue4770 messages
2009-12-14 19:03:28floxcreate