Re: [Python-Dev] Sad status of Python 3.x buildbots

On 03Sep2014 11:47, Stephen J. Turnbull wrote: Nick Coghlan writes: > Sorry, I haven't been a very good maintainer for that buildbot (the main > reason it never graduated to the "stable" list). If you send me your public > SSH key, I can add it (I think - if not, I can ask Luke to do it). > Alte

Re: [Python-Dev] Sad status of Python 3.x buildbots

Hello all I don't mind helping out with maintaining buildbots / other build machines. Although I don't have a lot of experience with this sort of thing (I usually just ran a Jenkins for my own work), I think it would be a useful way to contribute. Let me know what I should do if you are all fine wi

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Wed, Sep 3, 2014 at 12:47 PM, Stephen J. Turnbull wrote: > Nick Coghlan writes: > > > Sorry, I haven't been a very good maintainer for that buildbot (the main > > reason it never graduated to the "stable" list). If you send me your public > > SSH key, I can add it (I think - if not, I can as

Re: [Python-Dev] Sad status of Python 3.x buildbots

Nick Coghlan writes: > Sorry, I haven't been a very good maintainer for that buildbot (the main > reason it never graduated to the "stable" list). If you send me your public > SSH key, I can add it (I think - if not, I can ask Luke to do it). > Alternatively, CentOS 6 may exhibit the same prob

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

Antoine Pitrou writes: > On Tue, 2 Sep 2014 16:47:35 -0700 > Glyph Lefkowitz wrote: > > As we keep saying, this is not a break in backwards > > compatibility, it's a bug fix. > > Keeping saying it doesn't make it magically true. It's not "magically" true, it is "just" true. What the hard

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On Tue, 02 Sep 2014 20:59:54 -0400, Terry Reedy wrote: > On 9/2/2014 7:47 PM, Glyph Lefkowitz wrote: > > > > On Sep 2, 2014, at 4:28 PM, Nick Coghlan > > wrote: > > > >> On 3 Sep 2014 09:08, "David Reid" >> > wrote: > > >> > Clearly this change

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 9/2/2014 7:47 PM, Glyph Lefkowitz wrote: On Sep 2, 2014, at 4:28 PM, Nick Coghlan mailto:ncogh...@gmail.com>> wrote: On 3 Sep 2014 09:08, "David Reid" mailto:dr...@dreid.org>> wrote: > Clearly this change should be backported to Python2. Proposing to break backwards compatibility in a m

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Wed, 3 Sep 2014 08:53:51 +1000 Nick Coghlan wrote: > On 3 Sep 2014 08:15, "Victor Stinner" wrote: > > > > x86 RHEL 6 3.x: TestReadline.test_init() fails, issue #19884. I don't > > have to this platform, I don't know how to fix it. > > Sorry, I haven't been a very good maintainer for that buil

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Wed, 3 Sep 2014 00:13:22 +0200 Victor Stinner wrote: > > AMD64 Snow Leop 3.x: many tests are not reliable (stable) on this > platform. For example, test_logging.test_race() sometimes fail with > PermissionError(1, "Operation not permitted: > '/tmp/test_logging-3-bjulw8iz.log'"). Another exampl

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On Tue, 2 Sep 2014 16:47:35 -0700 Glyph Lefkowitz wrote: > > On Sep 2, 2014, at 4:28 PM, Nick Coghlan wrote: > > > On 3 Sep 2014 09:08, "David Reid" wrote: > > > > > > Nick Coghlan gmail.com> writes: > > > > > > > Creating *new* incompatibilities between Python 2 & Python 3 is a major > > >

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 03Sep2014 00:13, Victor Stinner wrote: AMD64 Snow Leop 3.x: many tests are not reliable (stable) on this platform. For example, test_logging.test_race() sometimes fail with PermissionError(1, "Operation not permitted: '/tmp/test_logging-3-bjulw8iz.log'"). Another example, test_asyncio.test_st

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

> On Sep 2, 2014, at 7:47 PM, Glyph Lefkowitz wrote: > > > On Sep 2, 2014, at 4:28 PM, Nick Coghlan > wrote: > >> On 3 Sep 2014 09:08, "David Reid" mailto:dr...@dreid.org>> >> wrote: >> > >> > Nick Coghlan gmail.com > writes: >> > >> > > Creatin

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On Sep 2, 2014, at 4:28 PM, Nick Coghlan wrote: > On 3 Sep 2014 09:08, "David Reid" wrote: > > > > Nick Coghlan gmail.com> writes: > > > > > Creating *new* incompatibilities between Python 2 & Python 3 is a major > > > point > > > of concern. > > > > Clearly this change should be backported t

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 3 Sep 2014 09:08, "David Reid" wrote: > > Nick Coghlan gmail.com> writes: > > > Creating *new* incompatibilities between Python 2 & Python 3 is a major point > > of concern. > > Clearly this change should be backported to Python2. Proposing to break backwards compatibility in a maintenance re

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On Sep 2, 2014, at 4:01 PM, Nick Coghlan wrote: > > On 3 Sep 2014 08:18, "Alex Gaynor" wrote: > > > > Antoine Pitrou pitrou.net> writes: > > > > > > > > And how many people are using Twisted as an HTTPS client? > > > (compared to e.g. Python's httplib, and all the third-party libraries > > >

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On Tue, 02 Sep 2014 22:16:18 -, Alex Gaynor wrote: > This whole scenario seems to be predicated on a siutation where: You have a > peer whose certificate you can't change, and you have a piece of code you > can't > change, and you're going to upgrade your Python installation, and you want to

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

Nick Coghlan gmail.com> writes: > Creating *new* incompatibilities between Python 2 & Python 3 is a major point > of concern. Clearly this change should be backported to Python2. -David ___ Python-Dev mailing list Python-Dev@python.org https://mail

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 3 Sep 2014 09:00, "Brian Curtin" wrote: > > On Tue, Sep 2, 2014 at 5:53 PM, Nick Coghlan wrote: >> >> From a completely different perspective, does anyone have experience with using BuildBot with OpenStack hosted clients? We may be able to take advantage of the PSF's new(ish) Rackspace infrast

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 3 Sep 2014 08:18, "Alex Gaynor" wrote: > > Antoine Pitrou pitrou.net> writes: > > > > > And how many people are using Twisted as an HTTPS client? > > (compared to e.g. Python's httplib, and all the third-party libraries > > building on it?) > > > > I don't think anyone could give an honest est

Re: [Python-Dev] Sad status of Python 3.x buildbots

On Tue, Sep 2, 2014 at 5:53 PM, Nick Coghlan wrote: > > On 3 Sep 2014 08:15, "Victor Stinner" wrote: > > > > x86 RHEL 6 3.x: TestReadline.test_init() fails, issue #19884. I don't > > have to this platform, I don't know how to fix it. > > Sorry, I haven't been a very good maintainer for that buil

Re: [Python-Dev] Sad status of Python 3.x buildbots

On 3 Sep 2014 08:15, "Victor Stinner" wrote: > > x86 RHEL 6 3.x: TestReadline.test_init() fails, issue #19884. I don't > have to this platform, I don't know how to fix it. Sorry, I haven't been a very good maintainer for that buildbot (the main reason it never graduated to the "stable" list). If

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 02.09.2014 23:32, Antoine Pitrou wrote: >> Furthermore, "disable verification" is a nonsensical thing to do with TLS. > > It's not. For example, if you have an expired cert, all you can do > AFAIK is to disable verification. It's possible to ignore or just warn about expired certs with simple

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On Tue, 2 Sep 2014 22:16:18 + (UTC) Alex Gaynor wrote: > > > Furthermore, "disable verification" is a nonsensical thing to do with TLS. > > > > It's not. For example, if you have an expired cert, all you can do > > AFAIK is to disable verification. > > It really is a nonsensical operation, a

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

Antoine Pitrou pitrou.net> writes: > > And how many people are using Twisted as an HTTPS client? > (compared to e.g. Python's httplib, and all the third-party libraries > building on it?) > I don't think anyone could give an honest estimate of these counts, however there's two factors to bare

[Python-Dev] Sad status of Python 3.x buildbots

Hi, I'm using Python buildbots to ensure that my changes don't fail on some platform. It's important for changes close to the operation system. The problem is that many buildbots are ill. Before, only a few buildbots had sporadic failures. Now most buildbots are always fail (are red). Here is an

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 1 Sep 2014 16:05, "Nick Coghlan" wrote: > > The final change would be to seed the context factory map > appropriately for the standard library modules where we wanted to keep > the *old* default: > > for modname in ("nntplib", "poplib", "imaplib", "ftplib", > "smtplib", "asyncio.selector_ev

Re: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR

2014-09-02 23:03 GMT+02:00 Matthew Woodcraft : > In any case I think PEP 475 should be explaining what is going to happen > to signal.siginterrupt(). Will setting flag=True be supported? I first proposed to deprecate the function, but Charles-François thinks that it's unrelated to the PEP (it can

Re: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR

2014-09-02 23:02 GMT+02:00 Matthew Woodcraft : > I think people who use sleep() in their programs could benefit from not > having to worry about EINTR as much as anyone else. The behaviour of time.sleep() is worse than what I expected. On UNIX, if select() fails with EINTR, time.sleep() calls PyE

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On Tue, 2 Sep 2014 14:00:02 -0700 Glyph Lefkowitz wrote: > > I would strongly recommend against such a mechanism. > > For what it's worth, Twisted simply unconditionally started verifying > certificates in 14.0 with no "disable" switch, and (to my knowledge) > literally no users have complaine

Re: [Python-Dev] https:bugs.python.org -- Untrusted Connection (Firefox)

On Tue, Sep 02, 2014 at 04:14:25PM -0400, Terry Reedy wrote: > On 9/2/2014 1:49 AM, Oleg Broytman wrote: > >On Mon, Sep 01, 2014 at 08:32:27PM -0500, Skip Montanaro > > wrote: > >>I got the same in Chrome on my Mac. > >> > >>Skip > >>On Sep 1, 2014 8:00 PM, "John Wong" wrote: > >> > >>>As of tod

Re: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR

Antoine Pitrou wrote: >Matthew Woodcraft wrote: >> (The program handles SIGTERM so that it can do a bit of cleanup before >> exiting, and it uses the signal-handler-sets-a-flag technique. The call >> that might be interrupted is sleep(), so the program doesn't strictly >> _rely_ on the existing

Re: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR

Nick Coghlan wrote: >On 2 September 2014 07:17, Matthew Woodcraft wrote: >> (The program handles SIGTERM so that it can do a bit of cleanup before >> exiting, and it uses the signal-handler-sets-a-flag technique. The call >> that might be interrupted is sleep(), so the program doesn't strictly >

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On Aug 29, 2014, at 7:44 PM, Alex Gaynor wrote: > Disabling verification entirely externally to the program, through a CLI flag > or environment variable. I'm pretty down on this idea, the problem you hit is > that it's a pretty blunt instrument to swing, and it's almost impossible to > imagin

Re: [Python-Dev] https:bugs.python.org -- Untrusted Connection (Firefox)

On 9/2/2014 1:49 AM, Oleg Broytman wrote: Hi! On Mon, Sep 01, 2014 at 08:32:27PM -0500, Skip Montanaro wrote: I got the same in Chrome on my Mac. Skip On Sep 1, 2014 8:00 PM, "John Wong" wrote: As of today I still am getting untrusted cert thought I would re-ping to see if there is an ETA

Re: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR

On Mon, 1 Sep 2014 21:17:33 + (UTC) Matthew Woodcraft wrote: > > > If such applications exist, they are not portable and are subject to > > race conditions (deadlock if the signal comes before the system call). > > The program is certainly not portable (which is not any kind of a > problem),

Re: [Python-Dev] https:bugs.python.org -- Untrusted Connection (Firefox)

On 2 September 2014 10:34, John Wong wrote: > As of today I still am getting untrusted cert thought I would re-ping to see > if there is an ETA. Thanks for the ping - I got sidetracked by other things, and didn't follow up on this one. I've kicked things into motion again, and it will hopefully b

Re: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR

On 2 September 2014 07:17, Matthew Woodcraft wrote: > > (The program handles SIGTERM so that it can do a bit of cleanup before > exiting, and it uses the signal-handler-sets-a-flag technique. The call > that might be interrupted is sleep(), so the program doesn't strictly > _rely_ on the existing