[issue23588] Errno conflicts in ssl.SSLError

Changes by Christian Heimes : -- assignee: christian.heimes -> ___ Python tracker ___ ___

[issue23588] Errno conflicts in ssl.SSLError

Changes by Christian Heimes : -- assignee: -> christian.heimes components: +SSL ___ Python tracker ___

[issue23588] Errno conflicts in ssl.SSLError

Changes by Giampaolo Rodola' : -- nosy: -giampaolo.rodola ___ Python tracker ___ ___

[issue23588] Errno conflicts in ssl.SSLError

Changes by Christian Heimes : -- versions: +Python 3.6, Python 3.7 -Python 3.4, Python 3.5 ___ Python tracker ___

[issue23588] Errno conflicts in ssl.SSLError

John Nagle added the comment: If SSL error reporting is getting some attention, something should be done to provide better text messages for the SSL errors. All certificate verify exceptions return the string certificate verify failed (_ssl.c:581). The line number in _ssl.c is not

[issue23588] Errno conflicts in ssl.SSLError

Antoine Pitrou added the comment: Theoretically, SSLError could stop inheriting from OSError. Practically, it may break a lot of code (though in a rather noisy way that is easy to spot). Otherwise, the best effort fix is to make our SSL error codes start at a high number, e.g. 2000 (but not

[issue23588] Errno conflicts in ssl.SSLError

Martin Panter added the comment: [padding] This behaviour of returning an SSL-specific error code in the “errno” attribute is not documented. The “errno” attribute is actually specified to hold a POSIX error code, and I don’t think this specification should be changed. I don’t see how

[issue23588] Errno conflicts in ssl.SSLError

Martin Panter added the comment: Okay I see your point about backwards compatibility now. Indeed, I have written code myself before Python 3.3 that used to inspect err.args[0], and it would suffer a similar problem if I had not updated it to use the new Python 3.3 exception subclasses. Below

[issue23588] Errno conflicts in ssl.SSLError

Ben Darnell added the comment: I agree that SSLError should have used a different attribute, but it's too late for that - changing it would break any code currently relying on SSL errnos (in particular asynchronous code using the SSL_ERROR_WANT_{READ,WRITE} error codes for normal operation).

[issue23588] Errno conflicts in ssl.SSLError

Martin Panter added the comment: Sorry I take back my claim that the error codes were undocumented; see the example code in https://docs.python.org/3.2/library/ssl.html#ssl-nonblocking. Perhaps the most compatible way to fix this would be to change the SSL error codes to something (custom

[issue23588] Errno conflicts in ssl.SSLError

Changes by Ned Deily n...@acm.org: -- nosy: +alex, christian.heimes, dstufft, giampaolo.rodola, janssen, pitrou versions: +Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23588

[issue23588] Errno conflicts in ssl.SSLError

New submission from Ben Darnell: ssl.SSLError is a subclass of OSError but uses error codes that come from a different scope than the standard errno constants and may have conflicts. For example, on my system (OSX), ssl.SSL_ERROR_WANT_X509_LOOKUP and errno.EINTR have the same value. This