[Python-Dev] Backwards compatibility after certificate autovalidation (original) (raw)
Cory Benfield cory at lukasa.co.uk
Mon Sep 8 21:44:52 CEST 2014
- Previous message: [Python-Dev] Backwards compatibility after certificate autovalidation
- Next message: [Python-Dev] Backwards compatibility after certificate autovalidation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 8 September 2014 18:23, Jim J. Jewett <jimjjewett at gmail.com> wrote:
Summary: There needs to be a simple way to opt out at install time. It would be far better to offer more fine-grained control, but leaving that better solution to downstream is acceptable.
Does this argument apply to a hypothetical 2.7 backport of this change, or does it apply to making the change in 3.5? (Or of course both.)
- Previous message: [Python-Dev] Backwards compatibility after certificate autovalidation
- Next message: [Python-Dev] Backwards compatibility after certificate autovalidation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]