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 kiilerix
Recipients kiilerix, loewis, pitrou
Date 2011-03-10.17:18:48
SpamBayes Score 0.00016913266
Marked as misclassified No
Message-id <1299777529.49.0.658773271399.issue10795@psf.upfronthosting.co.za>
In-reply-to
Content
The response I got to this issue hinted that it was a lame issue I filed. I haven't had time/focus to investigate further and give constructive feedback.

I think it is kind of OK to require explicit specification of the ca_certs as long as it is made clear in all the relevant places that it _has_ to be done. I think it would be a good idea to deprecate the default value for ca_certs and issue a warning if ca_certs hasn't been specified (as None or a path).

I have heard that some Python variants come with the system ca_certs built in and hard-coded somehow. That is in a way very nice and convenient and a good solution (as long the user wants to use the same ca_certs for all purposes), but it would have to be available and reliable on all platforms to be really useful.
History
Date User Action Args
2011-03-10 17:18:49kiilerixsetrecipients: + kiilerix, loewis, pitrou
2011-03-10 17:18:49kiilerixsetmessageid: <1299777529.49.0.658773271399.issue10795@psf.upfronthosting.co.za>
2011-03-10 17:18:48kiilerixlinkissue10795 messages
2011-03-10 17:18:48kiilerixcreate