Message 187772 - Python tracker

➜

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	serhiy.storchaka
Recipients	benjamin.peterson, lemburg, ncoghlan, serhiy.storchaka, vstinner
Date	2013-04-25.11:00:00
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1366887600.23.0.34103070344.issue17823@psf.upfronthosting.co.za>
In-reply-to

Content
> A more consistent alternative conversion: What advantages `codecs.encode("...", "base64_codec")` has comparing with `base64.b64encode("...")`? The latter is at least more portable and powerfull (it allows to specify altchars). I think that main problem with issue 7475 is that people don't think about a different (actually the most obvious) way to do base64 encoding.

> A more consistent alternative conversion:

What advantages `codecs.encode("...", "base64_codec")` has comparing with `base64.b64encode("...")`? The latter is at least more portable and powerfull (it allows to specify altchars).

I think that main problem with issue 7475 is that people don't think about a different (actually the most obvious) way to do base64 encoding.

History
Date	User	Action	Args
2013-04-25 11:00:00	serhiy.storchaka	set	recipients: + serhiy.storchaka, lemburg, ncoghlan, vstinner, benjamin.peterson
2013-04-25 11:00:00	serhiy.storchaka	set	messageid: <1366887600.23.0.34103070344.issue17823@psf.upfronthosting.co.za>
2013-04-25 11:00:00	serhiy.storchaka	link	issue17823 messages
2013-04-25 11:00:00	serhiy.storchaka	create