Message130516
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. |
|
Date |
User |
Action |
Args |
2011-03-10 17:18:49 | kiilerix | set | recipients:
+ kiilerix, loewis, pitrou |
2011-03-10 17:18:49 | kiilerix | set | messageid: <1299777529.49.0.658773271399.issue10795@psf.upfronthosting.co.za> |
2011-03-10 17:18:48 | kiilerix | link | issue10795 messages |
2011-03-10 17:18:48 | kiilerix | create | |
|