[issue17664] ssl.SSLError has errno value of None

New submission from Paul Wiseman: I was using py2.7.3 and was getting None back for the errno attribute for an ssl.SSLError('The read operation timed out'). I noticed in the 2.7.4 release notes that it sounds like there was a fix for this: Issue #12065: connect_ex() on an SSL socket now

[issue17664] ssl.SSLError has errno value of None

Paul Wiseman added the comment: Ah ok, thanks for clearing that up. I thought there'd have been a socket.error with ETIMEDOUT raised as the underlying exception, similar to if it times out during the non-ssl part of the request -- ___ Python

[issue16068] with statement executes type(obj).__exit__ rather than getattr(obj, __exit__)

New submission from Paul Wiseman: I found this behaviour today and thought it was weird so asked the question on SO here http://stackoverflow.com/questions/12632894/why-doesnt-getattr-work-with-exit/12632972#12632972 basically if I attributes are returned dynamically, they seem to get

[issue16068] with statement executes type(obj).__exit__ rather than getattr(obj, __exit__)

Paul Wiseman added the comment: I got pointed to an explanation in the docs! http://docs.python.org/reference/datamodel.html#special-method-lookup-for-new-style-classes It was confusing, though :) -- resolution: - invalid status: open - closed