I'd like to be able to backport this server-side SSL support to older Pythons, like the 2.3.4 in CentOS 4 and the 2.3.5 in OS X 10.4.
So I'd like to move all the SSL stuff out of the "socket" module, and add a new top-level module called "ssl" (or "networking.ssl", or whatever the Py3K naming scheme says it should be). The socket module will then re-export a function from that module as socket.ssl(), which will continue to do exactly what it does now. More advanced users will call functions in the "ssl" module. Then I can bundle up the new versions of _ssl.c and ssl.py with a setup.py file, and provide that as an add-on for older Python installations. Does this make sense? 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
