Re: [Python-Dev] PEP476: Enabling certificate validation by default

2014-09-20 Thread Guido van Rossum
OK, I'll hold off a bit on approving the PEP, but my intention is to approve it. Go Alex go! On Sat, Sep 20, 2014 at 4:03 PM, Nick Coghlan wrote: > On 21 September 2014 08:22, Guido van Rossum wrote: > > Sounds good. Maybe we should put the specifically targeted releases in > PEP > > 476? > > >

Re: [Python-Dev] PEP476: Enabling certificate validation by default

2014-09-20 Thread Nick Coghlan
On 21 September 2014 08:22, Guido van Rossum wrote: > Sounds good. Maybe we should put the specifically targeted releases in PEP > 476? > > Nick, do Christian's issues need to be mentioned in the PEP or should we > just keep those in the corresponding tracker items? They should be mentioned in th

[Python-Dev] web-sig mailing list moderating every post?

2014-09-20 Thread Robert Collins
I'm not sure of the right place to bring this up - I tried to on the web-sig list itself, but the moderator rejected the post. What I tried to post there was """Looks like *every* post to web-sig gets manually moderated. That seems like it will make discussion rather hard: can we get that changed

Re: [Python-Dev] PEP476: Enabling certificate validation by default

2014-09-20 Thread Guido van Rossum
Sounds good. Maybe we should put the specifically targeted releases in PEP 476? 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 wrote: > On 21 September 2014 03:05, Alex Ga

Re: [Python-Dev] web-sig mailing list moderating every post?

2014-09-20 Thread Robert Collins
Ugh - this was in my mailbox shortly after the moderator action email from mailman: "No, this looks like the spam filter. Don't know what triggered it. Or why it went to you. But the list moderation is turned off (except for non-members posting to the list), and you yourself are not moderated,

Re: [Python-Dev] PEP476: Enabling certificate validation by default

2014-09-20 Thread Nick Coghlan
On 21 September 2014 03:05, Alex Gaynor 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.

Re: [Python-Dev] PEP476: Enabling certificate validation by default

2014-09-20 Thread Alex Gaynor
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. Alex On Sat, Sep 20, 2014 at 9:46 AM, Guido van Rossum wrote: > Nice. I just realized the relea

Re: [Python-Dev] PEP476: Enabling certificate validation by default

2014-09-20 Thread Guido van Rossum
Nice. I just realized the release candidate for 3.4.2 is really close (RC1 Monday, final Oct 6, see PEP 429). What's your schedule for 3.4? I see no date for 2.7.9 yet (but that could just be that PEP 373 hasn't been updated). What about the Apple and Microsoft issues Christian pointed out? Regard

Re: [Python-Dev] PEP476: Enabling certificate validation by default

2014-09-20 Thread Alex Gaynor
Done and done. Alex On Fri, Sep 19, 2014 at 4:13 PM, Guido van Rossum wrote: > +1 on Nick's suggestion. (Might also mention that this is the reason why > both functions should exist and have compatible signatures.) > > Also please, please, please add explicit mention of Python 2.7, 3.4 and > 3.

Re: [Python-Dev] PEP476: Enabling certificate validation by default

2014-09-20 Thread Christian Heimes
On 19.09.2014 18:53, Alex Gaynor wrote: > Hi all, > > I've just updated the PEP to reflect the API suggestions from Nick, and the > fact that the necessary changes to urllib were landed. > > I think this is ready for pronouncement, Guido? There is still the issue with SSL_CERT_DIR and SSL_CERT_F