Author pitrou
Recipients christian.heimes, flox, jcea, pitrou, r.david.murray, sijinjoseph
Date 2013-04-07.15:29:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365348590.73.0.539320617088.issue17618@psf.upfronthosting.co.za>
In-reply-to
Content
The Mercurial authors have given their informal agreement for a relicensing. OTOH, they must still sign a contributor's agreement. The relicensing would allow us to use their pure Python implementation (in mercurial/pure/base85.py). OTOH, the C implementation (in mercurial/base85.c) is a ripoff of the git one, so we'd better rewrite our own.

My current plan would be the following:
- create a binascii.py and rename binascii.c to _binascii.c
- add Mercurial's pure Python implementation to binascii.py
- add a custom C implementation to _binascii.c
- make sure the binascii test suite tests both implementations

OTOH, if we don't get the Mercurial authors' contributor agreement, we can also re-write our own pure Python implementation.

In any case, our implementation should IMHO be compatible with Mercurial's (i.e. produce identical outputs for the same inputs).
History
Date User Action Args
2013-04-07 15:29:50pitrousetrecipients: + pitrou, jcea, christian.heimes, r.david.murray, flox, sijinjoseph
2013-04-07 15:29:50pitrousetmessageid: <1365348590.73.0.539320617088.issue17618@psf.upfronthosting.co.za>
2013-04-07 15:29:50pitroulinkissue17618 messages
2013-04-07 15:29:50pitroucreate