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 daniel.urban, debatem1, eric.araujo, exarkun, giampaolo.rodola, gregory.p.smith, heikki, loewis, mcrute, pitrou
Date 2010-06-15.13:21:11
SpamBayes Score 9.634508e-05
Marked as misclassified No
Message-id <1276608073.65.0.599603228222.issue8998@psf.upfronthosting.co.za>
In-reply-to
Content
I've taken a quick look at the source tree (there doesn't seem to be any separate docs) and here is my opinion:
- the evp.py API is too low-level (it's a one-to-one mapping to the OpenSSL C API); we would want at least some kind of object-oriented abstraction around the basic concepts (such as in the hashlib and ssl modules) rather than passing opaque pointers around
- the other APIs (cipher.py, envelope.py, signature.py) look conversely too high-level, since they focus on specific use cases and make some arbitrary choices for the user (for example, envelope.py imposes AES-192)

By the way, the use of function signature annotations to mirror C APIs as Python APIs through ctypes is nice, perhaps you should upload it as a separate library on PyPI :)
History
Date User Action Args
2010-06-15 13:21:14pitrousetrecipients: + pitrou, loewis, gregory.p.smith, exarkun, giampaolo.rodola, heikki, eric.araujo, debatem1, daniel.urban, mcrute
2010-06-15 13:21:13pitrousetmessageid: <1276608073.65.0.599603228222.issue8998@psf.upfronthosting.co.za>
2010-06-15 13:21:12pitroulinkissue8998 messages
2010-06-15 13:21:11pitroucreate