Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.c Subject: Re: Python recompile Date: Wed, 12 Mar 2025 06:50:46 -0000 (UTC) Organization: A noiseless patient Spider Lines: 30 Message-ID: References: <871pv861ht.fsf@nosuchdomain.example.com> <20250308192940.00001351@yahoo.com> <20250309012626.00001276@yahoo.com> <20250310135828.116@kylheku.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 12 Mar 2025 07:50:47 +0100 (CET) Injection-Info: dont-email.me; posting-host="e79dca7698d4321e2270f1d17dc9241d"; logging-data="2618196"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19AxSJ+OHnVmz6l/qPkF0yZ" User-Agent: Pan/0.162 (Pokrosvk) Cancel-Lock: sha1:lPPKraVVQbBP5nMtQVH/dlG6ij8= Bytes: 3027 On Tue, 11 Mar 2025 21:22:22 -0700, Chris M. Thomasson wrote: > On 3/11/2025 8:12 PM, Lawrence D'Oliveiro wrote: > >> On Tue, 11 Mar 2025 20:04:30 -0700, Chris M. Thomasson wrote: >> >>> IOCP works fine ... >> >> But not with pipes. > > Never tried them with pipes, only sockets. The Python developers have tried. They ended up creating two event loop implementations on Windows, neither of which quite covers all the bases . According to the platform support notes , SelectorEventLoop can only handle sockets (and has a limit of 512 of them), not pipes or subprocesses. ProactorEventLoop uses your favourite IOCP, but does not allow the addition of reader/writer callbacks for caller-supplied file descriptors. Neither one supports signal handlers. And there seems to be no Windows equivalent to Unix-style sockets. So on Windows, it’s a question of choosing which one is the least bad fit for your needs, and hoping you can make that work over your entire program.