Message 55516 - Python tracker

➜

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	janssen
Recipients	janssen
Date	2007-08-30.21:46:15
SpamBayes Score	0.077638485
Marked as misclassified	No
Message-id	<1188510375.86.0.454173087952.issue1065@psf.upfronthosting.co.za>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2007-08-30 21:46:15	janssen	set	spambayes_score: 0.0776385 -> 0.077638485 recipients: + janssen
2007-08-30 21:46:15	janssen	set	spambayes_score: 0.0776385 -> 0.0776385 messageid: <1188510375.86.0.454173087952.issue1065@psf.upfronthosting.co.za>
2007-08-30 21:46:15	janssen	link	issue1065 messages
2007-08-30 21:46:15	janssen	create