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 christian.heimes, ezio.melotti, pitrou
Date 2013-06-18.17:35:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371576940.3834.1.camel@fsol>
In-reply-to <1371576600.34.0.212060664957.issue18138@psf.upfronthosting.co.za>
Content
Le mardi 18 juin 2013 à 17:30 +0000, Christian Heimes a écrit :
> Christian Heimes added the comment:
> 
> I'm pondering about the error case "cert already in hash table". There
> should be a way to distinguish the error from other errors.

I don't know if you've seen it, but SSLError has "library" and "reason"
attributes (they are little known). See SSLErrorTests.

>  I see three ways to handle the case:
> 
> 1) introduce SSLCertInStoreError exeption
> 2) ignore the error and do nothing
> 3) ignore the error and return True if a cert was added or False if
> the cert is already in the store
> 
> I like 3).

Yes, sounds reasonable.
History
Date User Action Args
2013-06-18 17:35:48pitrousetrecipients: + pitrou, christian.heimes, ezio.melotti
2013-06-18 17:35:48pitroulinkissue18138 messages
2013-06-18 17:35:48pitroucreate