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 asdfasdfasdfasdfasdfasdfasdf
Recipients asdfasdfasdfasdfasdfasdfasdf, eric.araujo, loewis, pitrou
Date 2010-11-21.10:13:05
SpamBayes Score 3.2568192e-07
Marked as misclassified No
Message-id <AANLkTi=X7kP_mk=zudwwcKeDeW_Q8t4fEU3W+-iXooop@mail.gmail.com>
In-reply-to <4CE8EB47.6050009@v.loewis.de>
Content
On 21 November 2010 20:50, Martin v. Löwis <report@bugs.python.org> wrote:
>
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
>> So for python3 is it possible to make attempting to use capath(some
>> common ones OR the openssl location capath if this is ok for use) the
>> default(with failure to find a valid capath result in an exception
>> being raised) ?
>
> The default? That would be an incompatible change, and cause many
> complaints. So I'm very skeptical that this can be done.
>
> Having applications/scripts explicitly opt-in to a default CA
> certificate list would be an option (then making those applications
> break in installations where the default CA list is empty).

"Errors should never pass silently."
IMHO it is an error not to check by default.
No it wouldn't break anything that shouldn't break.
Users can then pass in None for the capath (as an example).
History
Date User Action Args
2010-11-21 10:13:06asdfasdfasdfasdfasdfasdfasdfsetrecipients: + asdfasdfasdfasdfasdfasdfasdf, loewis, pitrou, eric.araujo
2010-11-21 10:13:05asdfasdfasdfasdfasdfasdfasdflinkissue10441 messages
2010-11-21 10:13:05asdfasdfasdfasdfasdfasdfasdfcreate