Re: [python-committers] [Python-Dev] Farewell, Python 3.4

[Benjamin Peterson]

Thank you for your service!

On Wed, May 8, 2019, at 08:37, Larry Hastings wrote:
> 
> 
> It's with a note of sadness that I announce the final retirement of 
> Python 3.4. The final release was back in March, but I didn't get 
> around to actually closing and deleting the 3.4 branch until this 
> morning.
> 
> Python 3.4 introduced many features we all enjoy in modern Python--the 
> asyncio, ensurepip, and enum packages, just to name three. It's a 
> release I hope we all remember fondly.
> 
> My eternal thanks to all the members of the release team that worked on 
> Python 3.4:
> 
> > Georg Brandl
> 
> > Julien Palard
> 
> > Martin von Löwis
> 
> > Ned Deily
> 
> > Steve Dower
> 
> > Terry Reedy
> 
> > and all the engineers of the Python infrastructure team.
> 
> Special thanks to Benjamin Peterson and Ned Deily, who frequently 
> scurried around behind the scenes cleaning up the messes I cluelessly 
> left in my wake.
> 
> Having closed 3.4, I am now retired as Python 3.4 Release Manager. I 
> regret to inform all of you that you're still stuck with me as Python 
> 3.5 Release Manager until sometime next year.
> 
> 
> 
> My very best wishes,
> 
> 
> 
> */arry*
> 
> ___
> Python-Dev mailing list
> python-...@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/benjamin%40python.org
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] [Python-Dev] Farewell, Python 3.4

[Terry Reedy]

On 5/8/2019 11:46 AM, M.-A. Lemburg wrote:

Thank you for having been 3.4 release manager, Larry !


I especially appreciate being able to have proper signatures for builtin 
functions.


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] miss-islington backport pipeline is stalled?

[Mariatta]

We don't have sentry (I will ask Ernest about it), but such errors are
already sent to Zulip (
https://python.zulipchat.com/#narrow/stream/142203-workflow.2Fbot-api.20rate.20limit/topic/alerts/near/165174773)
and core-workflow
https://github.com/python/core-workflow/issues/257#issuecomment-490541831
But posting back to the PR itself will still be useful.
ᐧ

On Wed, May 8, 2019 at 10:04 AM Alex Gaynor  wrote:

> Would it make sense to work with the PSF infra staff so that
> miss-isslington is hooked up to the PSF Sentry account so folks can get
> email notifications and similar on unhandled exceptions?
>
> Alex
>
> On Wed, May 8, 2019 at 1:02 PM Mariatta  wrote:
>
>> There was an error from Redis. I think this is the first time I've seen
>> it, so I don't have any resolution on how to fix it right now.  
>> I will look into handling the error and have miss-islington leave a
>> comment in the PR when there is such error.
>>
>> log:
>>
>> at=info method=POST path="/" host=miss-islington.herokuapp.com 
>> request_id=8de611a2-6112-4039-a425-97850ac989b0 fwd="140.82.115.15" 
>> dyno=web.1 connect=1ms service=1005ms status=200 bytes=168 protocol=https
>> May 08 09:35:15 miss-islington app/web.1: Traceback (most recent call last):
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py", line 
>> 600, in send_packed_command
>> May 08 09:35:15 miss-islington app/web.1: self._sock.sendall(item)
>> May 08 09:35:15 miss-islington app/web.1: TimeoutError: [Errno 110] 
>> Connection timed out
>> May 08 09:35:15 miss-islington app/web.1: During handling of the above 
>> exception, another exception occurred:
>> May 08 09:35:15 miss-islington app/web.1: Traceback (most recent call last):
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/kombu/connection.py", line 
>> 431, in _reraise_as_library_errors
>> May 08 09:35:15 miss-islington app/web.1: yield
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/celery/app/base.py", line 
>> 744, in send_task
>> May 08 09:35:15 miss-islington app/web.1: self.backend.on_task_call(P, 
>> task_id)
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py", 
>> line 265, in on_task_call
>> May 08 09:35:15 miss-islington app/web.1: 
>> self.result_consumer.consume_from(task_id)
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py", 
>> line 126, in consume_from
>> May 08 09:35:15 miss-islington app/web.1: self._consume_from(task_id)
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py", 
>> line 132, in _consume_from
>> May 08 09:35:15 miss-islington app/web.1: self._pubsub.subscribe(key)
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/redis/client.py", line 
>> 3096, in subscribe
>> May 08 09:35:15 miss-islington app/web.1: ret_val = 
>> self.execute_command('SUBSCRIBE', *iterkeys(new_channels))
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/redis/client.py", line 
>> 3009, in execute_command
>> May 08 09:35:15 miss-islington app/web.1: self._execute(connection, 
>> connection.send_command, *args)
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/redis/client.py", line 
>> 3013, in _execute
>> May 08 09:35:15 miss-islington app/web.1: return command(*args)
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py", line 
>> 620, in send_command
>> May 08 09:35:15 miss-islington app/web.1: 
>> self.send_packed_command(self.pack_command(*args))
>> May 08 09:35:15 miss-islington app/web.1:   File 
>> "/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py", line 
>> 613, in send_packed_command
>> May 08 09:35:15 miss-islington app/web.1: (errno, errmsg))
>> May 08 09:35:15 miss-islington app/web.1: redis.exceptions.ConnectionError: 
>> Error 110 while writing to socket. Connection timed out.
>>
>>
>>
>> ᐧ
>>
>> On Wed, May 8, 2019 at 9:44 AM Gregory P. Smith  wrote:
>>
>>> Yesterday it failed to produce a backport or tell me that it couldn't
>>> (after the "i'm now working on ..." message was left on the master PR).  I
>>> waited a couple hours just in case and ran cherry_picker myself instead.
>>> Same thing today apparently on
>>> https://github.com/python/cpython/pull/13192 assuming the usual
>>> backport latency is no more than a minute or two.
>>>
>>> -gps
>>> ___
>>> python-committers mailing list
>>> python-committers@python.org
>>> 

Re: [python-committers] Merge with spurious CI failures?

[Gregory P. Smith]

fwiw a future way to avoid this mess is in
https://bugs.python.org/issue36855: have the tests support multiple
certificates so we can stage the new ones into our repo before updating the
server.

-gps

On Wed, May 8, 2019 at 11:15 AM Gregory P. Smith  wrote:

> If this cert change is impacting CI checks for everyone's PRs, I suspect
> all PRs will need to merge this change into their branch before they can
> pass CI.
>
> Having CI depend on external network resources does not seem like a good
> idea.
>
> -gps
>
> On Wed, May 8, 2019 at 11:04 AM Antoine Pitrou  wrote:
>
>>
>> Ah, there's already a PR at
>> https://github.com/python/cpython/pull/13192, thanks to Gregory.
>>
>> Regards
>>
>> Antoine.
>>
>>
>> Le 08/05/2019 à 17:58, Antoine Pitrou a écrit :
>> >
>> > Ok, apparently the SSL cert on self-signed.pythontest.net was changed
>> > but it wasn't updated in our source tree, hence the failure.
>> >
>> > Regards
>> >
>> > Antoine.
>> >
>> >
>> > Le 08/05/2019 à 17:49, Mariatta a écrit :
>> >> If you can't merge from GitHub UI then you won't be able to do it from
>> >> GitHub command line (it respects the same branch protection policy)
>> >>
>> >> I don't think we should merge if tests are still failing. Perhaps the
>> >> test should be adjusted to handle this spurious errors? Can it be
>> marked
>> >> as "allowed failure" or something like that?
>> >>
>> >>
>> >> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou > >> > wrote:
>> >>
>> >>
>> >> Hello,
>> >>
>> >> There are spurious CI failures (SSL certificate issue in
>> test_httplib).
>> >> Therefore the "Squash and merge" button is greyed out.
>> >>
>> >> How should I merge? Using the command-line instructions from
>> Github?
>> >>
>> >> Regards
>> >>
>> >> Antoine.
>> >> ___
>> >> python-committers mailing list
>> >> python-committers@python.org 
>> >> https://mail.python.org/mailman/listinfo/python-committers
>> >> Code of Conduct: https://www.python.org/psf/codeofconduct/
>> >>
>> > ___
>> > python-committers mailing list
>> > python-committers@python.org
>> > https://mail.python.org/mailman/listinfo/python-committers
>> > Code of Conduct: https://www.python.org/psf/codeofconduct/
>> >
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] miss-islington backport pipeline is stalled?

[Alex Gaynor]

Would it make sense to work with the PSF infra staff so that
miss-isslington is hooked up to the PSF Sentry account so folks can get
email notifications and similar on unhandled exceptions?

Alex

On Wed, May 8, 2019 at 1:02 PM Mariatta  wrote:

> There was an error from Redis. I think this is the first time I've seen
> it, so I don't have any resolution on how to fix it right now.  
> I will look into handling the error and have miss-islington leave a
> comment in the PR when there is such error.
>
> log:
>
> at=info method=POST path="/" host=miss-islington.herokuapp.com 
> request_id=8de611a2-6112-4039-a425-97850ac989b0 fwd="140.82.115.15" 
> dyno=web.1 connect=1ms service=1005ms status=200 bytes=168 protocol=https
> May 08 09:35:15 miss-islington app/web.1: Traceback (most recent call last):
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py", line 
> 600, in send_packed_command
> May 08 09:35:15 miss-islington app/web.1: self._sock.sendall(item)
> May 08 09:35:15 miss-islington app/web.1: TimeoutError: [Errno 110] 
> Connection timed out
> May 08 09:35:15 miss-islington app/web.1: During handling of the above 
> exception, another exception occurred:
> May 08 09:35:15 miss-islington app/web.1: Traceback (most recent call last):
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/kombu/connection.py", line 
> 431, in _reraise_as_library_errors
> May 08 09:35:15 miss-islington app/web.1: yield
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/celery/app/base.py", line 
> 744, in send_task
> May 08 09:35:15 miss-islington app/web.1: self.backend.on_task_call(P, 
> task_id)
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py", 
> line 265, in on_task_call
> May 08 09:35:15 miss-islington app/web.1: 
> self.result_consumer.consume_from(task_id)
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py", 
> line 126, in consume_from
> May 08 09:35:15 miss-islington app/web.1: self._consume_from(task_id)
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py", 
> line 132, in _consume_from
> May 08 09:35:15 miss-islington app/web.1: self._pubsub.subscribe(key)
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/redis/client.py", line 3096, 
> in subscribe
> May 08 09:35:15 miss-islington app/web.1: ret_val = 
> self.execute_command('SUBSCRIBE', *iterkeys(new_channels))
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/redis/client.py", line 3009, 
> in execute_command
> May 08 09:35:15 miss-islington app/web.1: self._execute(connection, 
> connection.send_command, *args)
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/redis/client.py", line 3013, 
> in _execute
> May 08 09:35:15 miss-islington app/web.1: return command(*args)
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py", line 
> 620, in send_command
> May 08 09:35:15 miss-islington app/web.1: 
> self.send_packed_command(self.pack_command(*args))
> May 08 09:35:15 miss-islington app/web.1:   File 
> "/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py", line 
> 613, in send_packed_command
> May 08 09:35:15 miss-islington app/web.1: (errno, errmsg))
> May 08 09:35:15 miss-islington app/web.1: redis.exceptions.ConnectionError: 
> Error 110 while writing to socket. Connection timed out.
>
>
>
> ᐧ
>
> On Wed, May 8, 2019 at 9:44 AM Gregory P. Smith  wrote:
>
>> Yesterday it failed to produce a backport or tell me that it couldn't
>> (after the "i'm now working on ..." message was left on the master PR).  I
>> waited a couple hours just in case and ran cherry_picker myself instead.
>> Same thing today apparently on
>> https://github.com/python/cpython/pull/13192 assuming the usual backport
>> latency is no more than a minute or two.
>>
>> -gps
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>


-- 
All that is necessary for evil to succeed is for good people to do nothing.
___
python-committers mailing list

Re: [python-committers] miss-islington backport pipeline is stalled?

[Mariatta]

There was an error from Redis. I think this is the first time I've seen it,
so I don't have any resolution on how to fix it right now.  
I will look into handling the error and have miss-islington leave a comment
in the PR when there is such error.

log:

at=info method=POST path="/" host=miss-islington.herokuapp.com
request_id=8de611a2-6112-4039-a425-97850ac989b0 fwd="140.82.115.15"
dyno=web.1 connect=1ms service=1005ms status=200 bytes=168
protocol=https
May 08 09:35:15 miss-islington app/web.1: Traceback (most recent call last):
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py",
line 600, in send_packed_command
May 08 09:35:15 miss-islington app/web.1: self._sock.sendall(item)
May 08 09:35:15 miss-islington app/web.1: TimeoutError: [Errno 110]
Connection timed out
May 08 09:35:15 miss-islington app/web.1: During handling of the above
exception, another exception occurred:
May 08 09:35:15 miss-islington app/web.1: Traceback (most recent call last):
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/kombu/connection.py",
line 431, in _reraise_as_library_errors
May 08 09:35:15 miss-islington app/web.1: yield
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/celery/app/base.py",
line 744, in send_task
May 08 09:35:15 miss-islington app/web.1:
self.backend.on_task_call(P, task_id)
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py",
line 265, in on_task_call
May 08 09:35:15 miss-islington app/web.1:
self.result_consumer.consume_from(task_id)
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py",
line 126, in consume_from
May 08 09:35:15 miss-islington app/web.1: self._consume_from(task_id)
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/celery/backends/redis.py",
line 132, in _consume_from
May 08 09:35:15 miss-islington app/web.1: self._pubsub.subscribe(key)
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/redis/client.py",
line 3096, in subscribe
May 08 09:35:15 miss-islington app/web.1: ret_val =
self.execute_command('SUBSCRIBE', *iterkeys(new_channels))
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/redis/client.py",
line 3009, in execute_command
May 08 09:35:15 miss-islington app/web.1:
self._execute(connection, connection.send_command, *args)
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/redis/client.py",
line 3013, in _execute
May 08 09:35:15 miss-islington app/web.1: return command(*args)
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py",
line 620, in send_command
May 08 09:35:15 miss-islington app/web.1:
self.send_packed_command(self.pack_command(*args))
May 08 09:35:15 miss-islington app/web.1:   File
"/app/.heroku/python/lib/python3.6/site-packages/redis/connection.py",
line 613, in send_packed_command
May 08 09:35:15 miss-islington app/web.1: (errno, errmsg))
May 08 09:35:15 miss-islington app/web.1:
redis.exceptions.ConnectionError: Error 110 while writing to socket.
Connection timed out.



ᐧ

On Wed, May 8, 2019 at 9:44 AM Gregory P. Smith  wrote:

> Yesterday it failed to produce a backport or tell me that it couldn't
> (after the "i'm now working on ..." message was left on the master PR).  I
> waited a couple hours just in case and ran cherry_picker myself instead.
> Same thing today apparently on
> https://github.com/python/cpython/pull/13192 assuming the usual backport
> latency is no more than a minute or two.
>
> -gps
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] miss-islington backport pipeline is stalled?

[Gregory P. Smith]

Yesterday it failed to produce a backport or tell me that it couldn't
(after the "i'm now working on ..." message was left on the master PR).  I
waited a couple hours just in case and ran cherry_picker myself instead.
Same thing today apparently on
https://github.com/python/cpython/pull/13192 assuming
the usual backport latency is no more than a minute or two.

-gps
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Gregory P. Smith]

If this cert change is impacting CI checks for everyone's PRs, I suspect
all PRs will need to merge this change into their branch before they can
pass CI.

Having CI depend on external network resources does not seem like a good
idea.

-gps

On Wed, May 8, 2019 at 11:04 AM Antoine Pitrou  wrote:

>
> Ah, there's already a PR at
> https://github.com/python/cpython/pull/13192, thanks to Gregory.
>
> Regards
>
> Antoine.
>
>
> Le 08/05/2019 à 17:58, Antoine Pitrou a écrit :
> >
> > Ok, apparently the SSL cert on self-signed.pythontest.net was changed
> > but it wasn't updated in our source tree, hence the failure.
> >
> > Regards
> >
> > Antoine.
> >
> >
> > Le 08/05/2019 à 17:49, Mariatta a écrit :
> >> If you can't merge from GitHub UI then you won't be able to do it from
> >> GitHub command line (it respects the same branch protection policy)
> >>
> >> I don't think we should merge if tests are still failing. Perhaps the
> >> test should be adjusted to handle this spurious errors? Can it be marked
> >> as "allowed failure" or something like that?
> >>
> >>
> >> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  >> > wrote:
> >>
> >>
> >> Hello,
> >>
> >> There are spurious CI failures (SSL certificate issue in
> test_httplib).
> >> Therefore the "Squash and merge" button is greyed out.
> >>
> >> How should I merge? Using the command-line instructions from Github?
> >>
> >> Regards
> >>
> >> Antoine.
> >> ___
> >> python-committers mailing list
> >> python-committers@python.org 
> >> https://mail.python.org/mailman/listinfo/python-committers
> >> Code of Conduct: https://www.python.org/psf/codeofconduct/
> >>
> > ___
> > python-committers mailing list
> > python-committers@python.org
> > https://mail.python.org/mailman/listinfo/python-committers
> > Code of Conduct: https://www.python.org/psf/codeofconduct/
> >
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Gregory P. Smith]

Our pythontestdotnet repo is different than the cpython repo and the
certificate gets pushed to the server after being committed by hand so it's
a synchronization problem,.

https://github.com/python/cpython/pull/13192 should clear it up.  It's
awaiting the slow CI queuing gods.  It is marked automerge, so if a core
dev could go do a github review and Approve it, it'll go in immediately
after Travis and AppVeyor come back green.

-gps

On Wed, May 8, 2019 at 10:58 AM Antoine Pitrou  wrote:

>
> Ok, apparently the SSL cert on self-signed.pythontest.net was changed
> but it wasn't updated in our source tree, hence the failure.
>
> Regards
>
> Antoine.
>
>
> Le 08/05/2019 à 17:49, Mariatta a écrit :
> > If you can't merge from GitHub UI then you won't be able to do it from
> > GitHub command line (it respects the same branch protection policy)
> >
> > I don't think we should merge if tests are still failing. Perhaps the
> > test should be adjusted to handle this spurious errors? Can it be marked
> > as "allowed failure" or something like that?
> >
> >
> > On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  > > wrote:
> >
> >
> > Hello,
> >
> > There are spurious CI failures (SSL certificate issue in
> test_httplib).
> > Therefore the "Squash and merge" button is greyed out.
> >
> > How should I merge? Using the command-line instructions from Github?
> >
> > Regards
> >
> > Antoine.
> > ___
> > python-committers mailing list
> > python-committers@python.org 
> > https://mail.python.org/mailman/listinfo/python-committers
> > Code of Conduct: https://www.python.org/psf/codeofconduct/
> >
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Antoine Pitrou]

Ah, there's already a PR at
https://github.com/python/cpython/pull/13192, thanks to Gregory.

Regards

Antoine.


Le 08/05/2019 à 17:58, Antoine Pitrou a écrit :
> 
> Ok, apparently the SSL cert on self-signed.pythontest.net was changed
> but it wasn't updated in our source tree, hence the failure.
> 
> Regards
> 
> Antoine.
> 
> 
> Le 08/05/2019 à 17:49, Mariatta a écrit :
>> If you can't merge from GitHub UI then you won't be able to do it from
>> GitHub command line (it respects the same branch protection policy)
>>
>> I don't think we should merge if tests are still failing. Perhaps the
>> test should be adjusted to handle this spurious errors? Can it be marked
>> as "allowed failure" or something like that?
>>
>>
>> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou > > wrote:
>>
>>
>> Hello,
>>
>> There are spurious CI failures (SSL certificate issue in test_httplib).
>> Therefore the "Squash and merge" button is greyed out.
>>
>> How should I merge? Using the command-line instructions from Github?
>>
>> Regards
>>
>> Antoine.
>> ___
>> python-committers mailing list
>> python-committers@python.org 
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Alex Gaynor]

https://github.com/python/cpython/pull/13192

Thanks gps!

Alex

On Wed, May 8, 2019 at 11:58 AM Antoine Pitrou  wrote:

>
> Ok, apparently the SSL cert on self-signed.pythontest.net was changed
> but it wasn't updated in our source tree, hence the failure.
>
> Regards
>
> Antoine.
>
>
> Le 08/05/2019 à 17:49, Mariatta a écrit :
> > If you can't merge from GitHub UI then you won't be able to do it from
> > GitHub command line (it respects the same branch protection policy)
> >
> > I don't think we should merge if tests are still failing. Perhaps the
> > test should be adjusted to handle this spurious errors? Can it be marked
> > as "allowed failure" or something like that?
> >
> >
> > On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  > > wrote:
> >
> >
> > Hello,
> >
> > There are spurious CI failures (SSL certificate issue in
> test_httplib).
> > Therefore the "Squash and merge" button is greyed out.
> >
> > How should I merge? Using the command-line instructions from Github?
> >
> > Regards
> >
> > Antoine.
> > ___
> > python-committers mailing list
> > python-committers@python.org 
> > https://mail.python.org/mailman/listinfo/python-committers
> > Code of Conduct: https://www.python.org/psf/codeofconduct/
> >
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>


-- 
All that is necessary for evil to succeed is for good people to do nothing.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Antoine Pitrou]

Ok, apparently the SSL cert on self-signed.pythontest.net was changed
but it wasn't updated in our source tree, hence the failure.

Regards

Antoine.


Le 08/05/2019 à 17:49, Mariatta a écrit :
> If you can't merge from GitHub UI then you won't be able to do it from
> GitHub command line (it respects the same branch protection policy)
> 
> I don't think we should merge if tests are still failing. Perhaps the
> test should be adjusted to handle this spurious errors? Can it be marked
> as "allowed failure" or something like that?
> 
> 
> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  > wrote:
> 
> 
> Hello,
> 
> There are spurious CI failures (SSL certificate issue in test_httplib).
> Therefore the "Squash and merge" button is greyed out.
> 
> How should I merge? Using the command-line instructions from Github?
> 
> Regards
> 
> Antoine.
> ___
> python-committers mailing list
> python-committers@python.org 
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Eric V. Smith]

D’oh! Good point!

Eric

> On May 8, 2019, at 11:52 AM, Alex Gaynor  wrote:
> 
> Tests for that PR would presumably be green :-)
> 
> Alex
> 
>> On Wed, May 8, 2019 at 11:51 AM Eric V. Smith  wrote:
>> Surely there must be some way around it. After all, how would you merge a PR 
>> to fix this test?
>> 
>> --
>> Eric V. Smith
>> True Blade Systems, Inc
>> (301) 859-4544
>> 
>>> On May 8, 2019, at 11:49 AM, Mariatta  wrote:
>>> 
>>> If you can't merge from GitHub UI then you won't be able to do it from 
>>> GitHub command line (it respects the same branch protection policy)
>>> 
>>> I don't think we should merge if tests are still failing. Perhaps the test 
>>> should be adjusted to handle this spurious errors? Can it be marked as 
>>> "allowed failure" or something like that?
>>> 
>>> 
 On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  wrote:
 
 Hello,
 
 There are spurious CI failures (SSL certificate issue in test_httplib).
 Therefore the "Squash and merge" button is greyed out.
 
 How should I merge? Using the command-line instructions from Github?
 
 Regards
 
 Antoine.
 ___
 python-committers mailing list
 python-committers@python.org
 https://mail.python.org/mailman/listinfo/python-committers
 Code of Conduct: https://www.python.org/psf/codeofconduct/
>>> ___
>>> python-committers mailing list
>>> python-committers@python.org
>>> https://mail.python.org/mailman/listinfo/python-committers
>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 
> 
> -- 
> All that is necessary for evil to succeed is for good people to do nothing.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Alex Gaynor]

Tests for that PR would presumably be green :-)

Alex

On Wed, May 8, 2019 at 11:51 AM Eric V. Smith  wrote:

> Surely there must be some way around it. After all, how would you merge a
> PR to fix this test?
>
> --
> Eric V. Smith
> True Blade Systems, Inc
> (301) 859-4544
>
> On May 8, 2019, at 11:49 AM, Mariatta  wrote:
>
> If you can't merge from GitHub UI then you won't be able to do it from
> GitHub command line (it respects the same branch protection policy)
>
> I don't think we should merge if tests are still failing. Perhaps the test
> should be adjusted to handle this spurious errors? Can it be marked as
> "allowed failure" or something like that?
>
>
> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  wrote:
>
>>
>> Hello,
>>
>> There are spurious CI failures (SSL certificate issue in test_httplib).
>> Therefore the "Squash and merge" button is greyed out.
>>
>> How should I merge? Using the command-line instructions from Github?
>>
>> Regards
>>
>> Antoine.
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>


-- 
All that is necessary for evil to succeed is for good people to do nothing.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Alex Gaynor]

I don't know if CPython has a specific policy about this -- other projects
I work on generally have a "we need to get master's tests passing again
before anything can merge" policy.

Alex

On Wed, May 8, 2019 at 11:44 AM Antoine Pitrou  wrote:

>
> They're deterministic.  Apparently the test which connects to
> "self-signed.pythontest.net" always fails now with a "self-signed
> certificate" error...
>
> Le 08/05/2019 à 17:37, Alex Gaynor a écrit :
> > Are these intermittent failures, or is there bustage on master right now?
> >
> > My usual habit on other projects (I'm not very active on CPython these
> > days) is to restart the build on travis so that is a nice green
> checkmark.
> >
> > Alex
> >
> > On Wed, May 8, 2019 at 11:32 AM Antoine Pitrou  > > wrote:
> >
> >
> > Hello,
> >
> > There are spurious CI failures (SSL certificate issue in
> test_httplib).
> > Therefore the "Squash and merge" button is greyed out.
> >
> > How should I merge? Using the command-line instructions from Github?
> >
> > Regards
> >
> > Antoine.
> > ___
> > python-committers mailing list
> > python-committers@python.org 
> > https://mail.python.org/mailman/listinfo/python-committers
> > Code of Conduct: https://www.python.org/psf/codeofconduct/
> >
> >
> >
> > --
> > All that is necessary for evil to succeed is for good people to do
> nothing.
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>


-- 
All that is necessary for evil to succeed is for good people to do nothing.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] [Python-Dev] Farewell, Python 3.4

[M.-A. Lemburg]

Thank you for having been 3.4 release manager, Larry !

On 08.05.2019 17:36, Larry Hastings wrote:
> 
> It's with a note of sadness that I announce the final retirement of
> Python 3.4.  The final release was back in March, but I didn't get
> around to actually closing and deleting the 3.4 branch until this morning.
> 
> Python 3.4 introduced many features we all enjoy in modern Python--the
> asyncio, ensurepip, and enum packages, just to name three.  It's a
> release I hope we all remember fondly.
> 
> My eternal thanks to all the members of the release team that worked on
> Python 3.4:
> 
> Georg Brandl
> 
> Julien Palard
> 
> Martin von Löwis
> 
> Ned Deily
> 
> Steve Dower
> 
> Terry Reedy
> 
> and all the engineers of the Python infrastructure team.
> 
> Special thanks to Benjamin Peterson and Ned Deily, who frequently
> scurried around behind the scenes cleaning up the messes I cluelessly
> left in my wake.
> 
> Having closed 3.4, I am now retired as Python 3.4 Release Manager.  I
> regret to inform all of you that you're still stuck with me as Python
> 3.5 Release Manager until sometime next year.
> 
> 
> My very best wishes,
> 
> 
> //arry/
> 
> 
> 
> ___
> Python-Dev mailing list
> python-...@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/mal%40egenix.com
> 

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, May 08 2019)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...   http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...   http://zope.egenix.com/


::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
   http://www.egenix.com/company/contact/
  http://www.malemburg.com/

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Eric V. Smith]

Surely there must be some way around it. After all, how would you merge a PR to 
fix this test?

--
Eric V. Smith
True Blade Systems, Inc
(301) 859-4544

> On May 8, 2019, at 11:49 AM, Mariatta  wrote:
> 
> If you can't merge from GitHub UI then you won't be able to do it from GitHub 
> command line (it respects the same branch protection policy)
> 
> I don't think we should merge if tests are still failing. Perhaps the test 
> should be adjusted to handle this spurious errors? Can it be marked as 
> "allowed failure" or something like that?
> 
> 
>> On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  wrote:
>> 
>> Hello,
>> 
>> There are spurious CI failures (SSL certificate issue in test_httplib).
>> Therefore the "Squash and merge" button is greyed out.
>> 
>> How should I merge? Using the command-line instructions from Github?
>> 
>> Regards
>> 
>> Antoine.
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Mariatta]

If you can't merge from GitHub UI then you won't be able to do it from
GitHub command line (it respects the same branch protection policy)

I don't think we should merge if tests are still failing. Perhaps the test
should be adjusted to handle this spurious errors? Can it be marked as
"allowed failure" or something like that?


On Wed, May 8, 2019, 8:32 AM Antoine Pitrou  wrote:

>
> Hello,
>
> There are spurious CI failures (SSL certificate issue in test_httplib).
> Therefore the "Squash and merge" button is greyed out.
>
> How should I merge? Using the command-line instructions from Github?
>
> Regards
>
> Antoine.
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Antoine Pitrou]

They're deterministic.  Apparently the test which connects to
"self-signed.pythontest.net" always fails now with a "self-signed
certificate" error...

Le 08/05/2019 à 17:37, Alex Gaynor a écrit :
> Are these intermittent failures, or is there bustage on master right now?
> 
> My usual habit on other projects (I'm not very active on CPython these
> days) is to restart the build on travis so that is a nice green checkmark.
> 
> Alex
> 
> On Wed, May 8, 2019 at 11:32 AM Antoine Pitrou  > wrote:
> 
> 
> Hello,
> 
> There are spurious CI failures (SSL certificate issue in test_httplib).
> Therefore the "Squash and merge" button is greyed out.
> 
> How should I merge? Using the command-line instructions from Github?
> 
> Regards
> 
> Antoine.
> ___
> python-committers mailing list
> python-committers@python.org 
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 
> 
> 
> -- 
> All that is necessary for evil to succeed is for good people to do nothing.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Merge with spurious CI failures?

[Alex Gaynor]

Are these intermittent failures, or is there bustage on master right now?

My usual habit on other projects (I'm not very active on CPython these
days) is to restart the build on travis so that is a nice green checkmark.

Alex

On Wed, May 8, 2019 at 11:32 AM Antoine Pitrou  wrote:

>
> Hello,
>
> There are spurious CI failures (SSL certificate issue in test_httplib).
> Therefore the "Squash and merge" button is greyed out.
>
> How should I merge? Using the command-line instructions from Github?
>
> Regards
>
> Antoine.
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>


-- 
All that is necessary for evil to succeed is for good people to do nothing.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Farewell, Python 3.4

[Larry Hastings]

It's with a note of sadness that I announce the final retirement of 
Python 3.4.  The final release was back in March, but I didn't get 
around to actually closing and deleting the 3.4 branch until this morning.


Python 3.4 introduced many features we all enjoy in modern Python--the 
asyncio, ensurepip, and enum packages, just to name three.  It's a 
release I hope we all remember fondly.


My eternal thanks to all the members of the release team that worked on 
Python 3.4:


   Georg Brandl

   Julien Palard

   Martin von Löwis

   Ned Deily

   Steve Dower

   Terry Reedy

   and all the engineers of the Python infrastructure team.

Special thanks to Benjamin Peterson and Ned Deily, who frequently 
scurried around behind the scenes cleaning up the messes I cluelessly 
left in my wake.


Having closed 3.4, I am now retired as Python 3.4 Release Manager.  I 
regret to inform all of you that you're still stuck with me as Python 
3.5 Release Manager until sometime next year.



My very best wishes,


//arry/

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Merge with spurious CI failures?

[Antoine Pitrou]

Hello,

There are spurious CI failures (SSL certificate issue in test_httplib).
Therefore the "Squash and merge" button is greyed out.

How should I merge? Using the command-line instructions from Github?

Regards

Antoine.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/