[Python-Dev] PEP476: Enabling certificate validation by default
Guido van Rossum
guido at python.org
Sun Sep 21 00:22:57 CEST 2014
Sounds good. Maybe we should put the specifically targeted releases in PEP
Nick, do Christian's issues need to be mentioned in the PEP or should we
just keep those in the corresponding tracker items?
On Sat, Sep 20, 2014 at 3:05 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 21 September 2014 03:05, Alex Gaynor <alex.gaynor at gmail.com> wrote:
> > That sounds reasonable to me -- at this point I don't expect this to
> make it
> > into 3.4.2; Nick has some working code on the ticket:
> > http://bugs.python.org/issue22417 it's mostly missing documentation.
> I also think it's more sensible to target 2.7.9 & 3.4.3 for this
> change, especially given the remaining rough edges in custom trust
> database configuration on WIndows and Mac OS X that Christian pointed
> out in http://bugs.python.org/issue22449
> I don't believe Benjamin has picked a specific date for 2.7.9 yet, but
> the regular maintenance release cadence (ignoring security releases)
> would put it some time in November, which should be sufficient time to
> get the remaining issues ironed out for 3.5 under the normal
> development process, and then included under the banner of PEP 476 for
> backporting to the maintenance branches.
> Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev