[issue8998] add crypto routines to stdlib

Antoine Pitrou report at bugs.python.org
Sun Sep 19 01:05:19 CEST 2010

Antoine Pitrou <pitrou at free.fr> added the comment:

> It is also not a convincing argument that new python libraries should
> use OpenSSL if possible just because that is what _ssl uses. Compiling
> Python with OpenSSL support has been optional because it puts
> additional restrictions on the PSF license. Spreading this restriction
> to the future crypto module (when we have a choice not to) doesn't
> make sense.

It certainly makes more sense than making Python depend on *several*
crypto libraries.
As for the licensing restriction, it doesn't seem to disturb many Python
users. It's the first time I see someone complaining about it.

This isn't meant to discourage any such efforts (I don't care about
which crypto library we use), but any proposal of using another crypto
library than OpenSSL should IMO include a migration proposal for the
_ssl module.


Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list