New submission from Bill Janssen: It seems like a bad idea to have ssl.sslsocket(socket) suddenly become ssl.SSLSocket(fileno) in 2.3. Since no user code is currently using the ssl module, it would be a good idea to change it upfront (if possible) so that code written against 2.6's version of the ssl module doesn't break gratuitously in 3.x.
Would suggest changing the class name now, not documenting the initializer, and adding a function (say, "wrap_socket") which takes a socket and the other init arguments to the current ssl.sslsocket(), which would continue to work the same way in 3.x. ---------- assignee: janssen components: Library (Lib) keywords: py3k messages: 55516 nosy: janssen priority: normal severity: normal status: open title: ssl.py shouldn't change class names from 2.6 to 3.x type: behavior versions: Python 2.6, Python 3.0 __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1065> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
