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 pitrou
Recipients exarkun, giampaolo.rodola, janssen, pitrou
Date 2010-08-30.15:22:54
SpamBayes Score 3.8269388e-13
Marked as misclassified No
Message-id <1283181776.09.0.242188827104.issue9711@psf.upfronthosting.co.za>
In-reply-to
Content
Not really, but in previous versions it would fail as soon as you try to connect:

>>> s = ssl.wrap_socket(socket.socket(), keyfile="XXX")
>>> s.connect(("svn.python.org", 443))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/antoine/cpython/27/Lib/ssl.py", line 295, in connect
    self.ca_certs, self.ciphers)
ssl.SSLError: _ssl.c:289: Both the key & certificate files must be specified

It's better to catch the problem up-front, though. As for whether SSLError or ValueError should be preferred, I think ValueError is cleaner (it's really a bad use of the API).
History
Date User Action Args
2010-08-30 15:22:56pitrousetrecipients: + pitrou, exarkun, janssen, giampaolo.rodola
2010-08-30 15:22:56pitrousetmessageid: <1283181776.09.0.242188827104.issue9711@psf.upfronthosting.co.za>
2010-08-30 15:22:54pitroulinkissue9711 messages
2010-08-30 15:22:54pitroucreate