Message 187186 - 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	christian.heimes, flox, isoschiz, jcea, pitrou, r.david.murray, serhiy.storchaka, sijinjoseph
Date	2013-04-17.18:14:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1366222482.66.0.480931794823.issue17618@psf.upfronthosting.co.za>
In-reply-to

Content
> btoa/atob seems extinct. At least half of ascii85 encoders in wild implement this variant. I think we can provide a universal solution compatible (with some pre/postprocessing) with both variants. Enclose encoded data in <~ and ~> or not, and at which column wrap an encoded data. Padding can be easy implemented as preprocessing (data + (-len(data)) % 4 * b'\0'). As for Git/Mercurial's base85, what other applications use this encoding?

> btoa/atob seems extinct.

At least half of ascii85 encoders in wild implement this variant.

I think we can provide a universal solution compatible (with some pre/postprocessing) with both variants. Enclose encoded data in <~ and ~> or not, and at which column wrap an encoded data. Padding can be easy implemented as preprocessing (data + (-len(data)) % 4 * b'\0').

As for Git/Mercurial's base85, what other applications use this encoding?

History
Date	User	Action	Args
2013-04-17 18:14:42	serhiy.storchaka	set	recipients: + serhiy.storchaka, jcea, pitrou, christian.heimes, r.david.murray, flox, sijinjoseph, isoschiz
2013-04-17 18:14:42	serhiy.storchaka	set	messageid: <1366222482.66.0.480931794823.issue17618@psf.upfronthosting.co.za>
2013-04-17 18:14:42	serhiy.storchaka	link	issue17618 messages
2013-04-17 18:14:42	serhiy.storchaka	create