Re: [PATCH 4 of 5] py3: stop subscripting socket.error

2018-12-15 Thread Yuya Nishihara
On Sun, 16 Dec 2018 01:19:47 -0500, Matt Harbison wrote: > On Sun, 16 Dec 2018 00:55:20 -0500, Yuya Nishihara wrote: > > > On Sun, 16 Dec 2018 00:36:45 -0500, Matt Harbison wrote: > >> > I'm not sure what to do with this info yet, but I just noticed that > >> > pager is also messed up on py3-

Re: [PATCH 4 of 5] py3: stop subscripting socket.error

2018-12-15 Thread Matt Harbison
On Sun, 16 Dec 2018 00:55:20 -0500, Yuya Nishihara wrote: On Sun, 16 Dec 2018 00:36:45 -0500, Matt Harbison wrote: > I'm not sure what to do with this info yet, but I just noticed that > pager is also messed up on py3- the debug message about spawning the > pager prints, but no output for the

Re: [PATCH 4 of 5] py3: stop subscripting socket.error

2018-12-15 Thread Yuya Nishihara
On Sun, 16 Dec 2018 00:36:45 -0500, Matt Harbison wrote: > > I'm not sure what to do with this info yet, but I just noticed that > > pager is also messed up on py3- the debug message about spawning the > > pager prints, but no output for the diff. Use --pager=no, and it shows > > up. So

Re: [PATCH 4 of 5] py3: stop subscripting socket.error

2018-12-15 Thread Matt Harbison
On Sat, 15 Dec 2018 23:58:13 -0500, Matt Harbison wrote: On Mon, 10 Dec 2018 07:12:41 -0500, Yuya Nishihara wrote: On Sun, 09 Dec 2018 23:39:33 -0500, Matt Harbison wrote: I ended up with similar stdio errors trying to track down the bad http status failures: Traceback (most recent call

Re: [PATCH 4 of 5] py3: stop subscripting socket.error

2018-12-15 Thread Matt Harbison
On Mon, 10 Dec 2018 07:12:41 -0500, Yuya Nishihara wrote: On Sun, 09 Dec 2018 23:39:33 -0500, Matt Harbison wrote: I ended up with similar stdio errors trying to track down the bad http status failures: Traceback (most recent call last): File "c:\Users\Matt\hg\mercurial\ui.py", line 1033,

Re: [PATCH 4 of 5] py3: stop subscripting socket.error

2018-12-10 Thread Yuya Nishihara
On Sun, 09 Dec 2018 23:39:33 -0500, Matt Harbison wrote: > I ended up with similar stdio errors trying to track down the bad http > status failures: > > Traceback (most recent call last): >File "c:\Users\Matt\hg\mercurial\ui.py", line 1033, in _writenobuf > dest.flush() > OSError:

Re: [PATCH 4 of 5] py3: stop subscripting socket.error

2018-12-09 Thread Matt Harbison
On Sun, 09 Dec 2018 22:44:36 -0500, Matt Harbison wrote: # HG changeset patch # User Matt Harbison # Date 1544402454 18000 # Sun Dec 09 19:40:54 2018 -0500 # Node ID e5b7d60068537baa1ffeeca4e1a81f7498d0d48e # Parent 8f35bbc97ab5ec0ab5072900b9a70cea8fe720d0 py3: stop subscripting

[PATCH 4 of 5] py3: stop subscripting socket.error

2018-12-09 Thread Matt Harbison
# HG changeset patch # User Matt Harbison # Date 1544402454 18000 # Sun Dec 09 19:40:54 2018 -0500 # Node ID e5b7d60068537baa1ffeeca4e1a81f7498d0d48e # Parent 8f35bbc97ab5ec0ab5072900b9a70cea8fe720d0 py3: stop subscripting socket.error In 3.3 and later, this is now an alias for OSError. I