Not necessarily. I have no problems with hashlib or Python/M2Crypto/OpenSSL as long as I'm doing memory-oriented operations. It is only when the function does I/O that errors occur. ...like reading/writing a PEM file, randpool.dat, etc.
-----Original Message----- From: Bill Janssen [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2008 5:54 PM To: Bugbee, Larry Cc: "Martin v. Löwis"; Koenig, Gerald; python-dev@python.org Subject: Re: [Python-Dev] Python for windows. Bugbee, Larry <[EMAIL PROTECTED]> wrote: > For most custom apps this is a simple process of adding "#include > applink.c" to the app's main(). The problem for Python developers is > that their Python program is not main(), and if python.exe does not > have the OPENSSL_Applink interface, they cannot import M2Crypto, > pyOpenSSL, or use ctypes to wrap OpenSSL, and write a PEM file without > throwing an error. (That said, Daniel Clark says he is not > experiencing problems with NCrypt. I have not verified.) I'm probably missing something here. Python 2.6/3.x uses OpenSSL for the hashlib and ssl modules. Doesn't this mean that this applink.c file is part of the standard build now? Bill _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
