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 loewis
Recipients flox, loewis, pitrou, wiggin15
Date 2010-09-30.15:39:13
SpamBayes Score 7.980632e-08
Marked as misclassified No
Message-id <1285861157.3.0.925124384443.issue9996@psf.upfronthosting.co.za>
In-reply-to
Content
-1 on this patch; I think any change must get consensus on python-dev first, and there is no point in resolving this in the bug tracker. If no agreement can be found (which is actually likely), a PEP needs to be written.

My personal favorite would be to a) leave the binascii module alone, and b) add more functions to the base64 module, taking and returning Unicode strings as encoded objects.

However, I really fail to see what's so bad about

  binascii.b2a_hex(B).decode('ascii')

Under the rule "not every two line function belongs into the standard library", I would then be -0 on adding it to base64.
History
Date User Action Args
2010-09-30 15:39:17loewissetrecipients: + loewis, pitrou, flox, wiggin15
2010-09-30 15:39:17loewissetmessageid: <1285861157.3.0.925124384443.issue9996@psf.upfronthosting.co.za>
2010-09-30 15:39:14loewislinkissue9996 messages
2010-09-30 15:39:13loewiscreate