From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <0BE4B21D-EDA9-4DF5-8515-7BA27841B3E3@corpus-callosum.com> Date: Tue, 26 Feb 2013 16:26:19 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e0117791316307204d6a31ea3 Subject: Re: [9fans] APE select() and awkward Python subprocess PIPEfitting Topicbox-Message-UUID: 201eae82-ead8-11e9-9d60-3106f5b1d025 --089e0117791316307204d6a31ea3 Content-Type: text/plain; charset=UTF-8 On 26 February 2013 16:20, Charles Forsyth wrote: > If APE's select does the same, it will be fine, without breaking Python's > pipes. "it will be fine" -- I meant X11 will be fine, since it's relying on closing a file descriptor in one part of the program to cause EBADF in the select in another part, which will cause it to check connections. But, but, why doesn't it just ... ? Never mind, I don't think we need to work that out, just behave in the same way as Linux select. --089e0117791316307204d6a31ea3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 26 February 2013 16:20, Charles Forsyth <charles.forsyth@gmail.= com> wrote:
If APE's select does the same, it will b= e fine, without breaking Python's pipes.

"it= will be fine" -- I meant X11 will be fine, since it's relying on = closing a file descriptor in
one part of the program to cause EBADF in = the select in another part, which will cause it
to check connections. But, but, why doesn't it just ... ? = =C2=A0Never mind, I don't think we need to work that out,
just behave in the same way as Linux selec= t.
--089e0117791316307204d6a31ea3--