Author christian.heimes
Recipients christian.heimes, ezio.melotti, pitrou
Date 2013-06-18.17:30:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371576600.34.0.212060664957.issue18138@psf.upfronthosting.co.za>
In-reply-to
Content
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 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).
History
Date User Action Args
2013-06-18 17:30:00christian.heimessetrecipients: + christian.heimes, pitrou, ezio.melotti
2013-06-18 17:30:00christian.heimessetmessageid: <1371576600.34.0.212060664957.issue18138@psf.upfronthosting.co.za>
2013-06-18 17:30:00christian.heimeslinkissue18138 messages
2013-06-18 17:30:00christian.heimescreate