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 kxroberto
Recipients Ramchandra Apte, barry, jcea, kxroberto, r.david.murray
Date 2011-12-11.18:07:22
SpamBayes Score 2.6761898e-08
Marked as misclassified No
Message-id <1323626843.68.0.0930638293538.issue13580@psf.upfronthosting.co.za>
In-reply-to
Content
"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 )
History
Date User Action Args
2011-12-11 18:07:23kxrobertosetrecipients: + kxroberto, barry, jcea, r.david.murray, Ramchandra Apte
2011-12-11 18:07:23kxrobertosetmessageid: <1323626843.68.0.0930638293538.issue13580@psf.upfronthosting.co.za>
2011-12-11 18:07:23kxrobertolinkissue13580 messages
2011-12-11 18:07:22kxrobertocreate