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 martin.panter
Recipients Ben.Darnell, alex, christian.heimes, dstufft, giampaolo.rodola, janssen, martin.panter, pitrou
Date 2015-03-08.00:55:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425776130.62.0.428177464433.issue23588@psf.upfronthosting.co.za>
In-reply-to
Content
[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 checking for an “errno_scope” attribute is any better than checking for isinstance(exception, SSLError). I think the SSL error codes should be removed from “errno”, or maybe moved to a new attribute (ssl_error?), like what is already done with the “winerror” attribute.
History
Date User Action Args
2015-03-08 00:55:30martin.pantersetrecipients: + martin.panter, janssen, pitrou, giampaolo.rodola, christian.heimes, alex, Ben.Darnell, dstufft
2015-03-08 00:55:30martin.pantersetmessageid: <1425776130.62.0.428177464433.issue23588@psf.upfronthosting.co.za>
2015-03-08 00:55:30martin.panterlinkissue23588 messages
2015-03-08 00:55:30martin.pantercreate