On Mon, Jun 14, 2010 at 3:09 PM, Martin v. Löwis <report@bugs.python.org> wrote:
>
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
> Assuming you are willing to contribute evpy (and have the rights to do so, i.e. all of the code is truly yours): what's the user acceptance of the code?

I'd be willing to, but I see more utility in contributing specific
elements of its
functionality to the stdlib. Obviously the code is mine, and I can relicense
as needed if necessary.

As for your second question, I don't believe it sees much in the way of use.

> In particular, what do authors of competing OpenSSL wrappers (like M2Crypto) or other Python crypto packages (like pycrypto) think about this idea?

Evpy and M2Crypto have very different goals. M2Crypto seeks to be a
complete wrapper for OpenSSL, which we don't, and also uses SWIG,
which disqualifies it from consideration for the stdlib.

I don't know what the pycrypto folks would say about evpy, but I admit
to being very wary of that project- it appears to have been constructed
in a way which lends itself well to academic exercise rather than
practical use by nonexperts, and have had multiple occasions to correct
its dire misuse.

Geremy Condra