kxroberto <kxrobe...@users.sourceforge.net> added the comment:

"Of course, as soon as we use sockets, we will bring SSL in"

Indeed, as it is now. 
Suggestions:


* urllib.URLOpener.open_https  shall always exist, but fail on runtime.  
non-existance with strange "AttributeError" is inelegant..bogus.
Note: concept of late import ftplib, .. is otherwise ok in urllib. same style 
shall be used for ssl on demand. see python-Bugs-1046077)

* httplib.HTTPSConnection.connect shall late-import ssl

* httplib.HTTPSConnection,HTTPS,FakeSocket shall always exist but error on 
runtime if ssl is not available; same reason as with open_https

(* httplib.test already late-imports ssl)

* imaplib.IMAP4_SSL.ssl,open shall late-import ssl

* smtplib.starttls should late-import ssl

* smtplib.SMTP_SSL._get_socket  should late-import ssl

* smtplib.SSLFakeFile shall always exist (same reason as with open_https)

* poplib.POP3_SSL.__init__ shall late-import ssl

* deprecated socket.ssl() shall late-import _ssl/ssl (and possibly      
RAND_add, RAND_egd, RAND_status too if they need to exist globally for 
compabtibilty; constants to be entered fix into socket or _socket; sslerror 
perhaps a builtin in _socket, which _ssl then uses )

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13580>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to