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 pitrou
Recipients christian.heimes, flox, isoschiz, jcea, pitrou, r.david.murray, serhiy.storchaka, sijinjoseph
Date 2013-04-17.18:21:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366222906.2556.7.camel@fsol>
In-reply-to <>
Le mercredi 17 avril 2013 à 18:14 +0000, Serhiy Storchaka a écrit :
> 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').

That's ok with me. It's just more work for whoever does it :-)

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

I don't know, but they use it to produce binary diffs ("diff" chunks of
binary files), so any application wanting to parse Mercurial/Git diffs
would have to recognize base85 data.

(and I also like that the Mercurial/Git variant is the simpler of all
3 :-))
Date User Action Args
2013-04-17 18:21:49pitrousetrecipients: + pitrou, jcea, christian.heimes, r.david.murray, flox, sijinjoseph, serhiy.storchaka, isoschiz
2013-04-17 18:21:48pitroulinkissue17618 messages
2013-04-17 18:21:48pitroucreate