Comment 11 for bug 502291

@Thorsten, I can defintely revive this patch (and add more documentation) as a github fork as soon as your python 3 work get merged into fork.

What is not clear to me is whether the proposed API (see patch description) is OK to you guys or not.

@Dwayne, note that this patch *extends* Crypto.PublicKey (which I agree is pretty horrible): it does not create a new API. However, it is backward compatible and at least it does not break any existing application using it.