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-07.17:18:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365355096.3373.5.camel@localhost.localdomain>
In-reply-to <>
> So I'm not sure what you want to do. I would suggest a standard
> Ascii85 encoder is definitely useful, and provides feature parity with
> Ruby. If we want the standard library to be able to read/write
> Mercurial/Git base64 encoded files, then I guess that can be added
> too. If we think RFC1924 is useful/used, then the implementation in
> the netaddr lib looks right.

Agreed for both the Ascii85 encoder and the hg/git brand of base85
(which is used for "binary diffs", by the way). I don't think supporting
RFC1924 is useful, though.

(I think using "ascii85" and "base85" for those encodings, respectively,
provides a nice way to distinguish them)
Date User Action Args
2013-04-07 17:18:29pitrousetrecipients: + pitrou, jcea, christian.heimes, r.david.murray, flox, sijinjoseph, serhiy.storchaka, isoschiz
2013-04-07 17:18:29pitroulinkissue17618 messages
2013-04-07 17:18:28pitroucreate