As I write this email I'm tagging Python 3.5.0 release candidate 1. This
is the moment that we switch over to our new experimental workflow,
where we use Bitbucket and pull requests for all future changesets that
will get applied to 3.5.0.
The Bitbucket repository isn't ready yet, and I'm s
Anyone else seeing this?
pulling from ssh://[email protected]/cpython
remote: ssh_exchange_identification: Connection closed by remote host
abort: no suitable response from remote hg!
My laptop is fairly new so I'm trying to eliminate any way it might be my
setup instead of the servers.
__
It finally worked, so it looks like this was a server hiccup that just
happened to last a little while.
On Sun, 9 Aug 2015 at 11:19 Brett Cannon wrote:
> Anyone else seeing this?
>
> pulling from ssh://[email protected]/cpython
> remote: ssh_exchange_identification: Connection closed by rem
> On Aug 9, 2015, at 14:19, Brett Cannon wrote:
>
> Anyone else seeing this?
>
> pulling from ssh://[email protected]/cpython
> remote: ssh_exchange_identification: Connection closed by remote host
> abort: no suitable response from remote hg!
>
> My laptop is fairly new so I'm trying
According to the infrastructure list/#python-infra, there is currently
some instability in the load balancers. That is probably the source of
these errors.
On Sun, 09 Aug 2015 14:45:27 -0400, Ned Deily wrote:
> > On Aug 9, 2015, at 14:19, Brett Cannon wrote:
> >
> > Anyone else seeing this?
>
