Martin v. Löwis <mar...@v.loewis.de> added the comment: > 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.
That isn't really my question; it's the other way 'round: what do *they* (i.e. the respective authors) say about evpy? In the absence of actual user input, support for inclusion of it by these experts would be a valuable indication that this specific library should be included. Likewise, objective resistance may lead to significant changes before inclusion, or to rejection. In the absence of both user support and expert opinions, I'd ask for a PEP. ---------- title: add encryption/decryption/signature/verification routines to stdlib -> add crypto routines to stdlib _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8998> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
