This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author beazley
Recipients amaury.forgeotdarc, beazley
Date 2008-12-29.18:54:17
SpamBayes Score 9.760543e-05
Marked as misclassified No
Message-id <>
Given the low-level nature of this module, I can understand the 
motivation to make it all bytes.

However, I'm going to respectfully disagree with that and claim that 
making binascii all bytes really goes against the whole spirit of what 
Python 3.0 has tried to do for Unicode.  For example, throughout Python, 
you now have a clean separation between binary data (bytes) and text 
data (str).   Well, it's cleanly separated everywhere except in the 
binascii module (and base64 module) which, ironically, is all about 
converting between binary data and text.

As it stands now, it's a huge wart IMHO.
Date User Action Args
2008-12-29 18:54:18beazleysetrecipients: + beazley, amaury.forgeotdarc
2008-12-29 18:54:18beazleysetmessageid: <>
2008-12-29 18:54:18beazleylinkissue4770 messages
2008-12-29 18:54:17beazleycreate