Re: Python (was Re: I did not inhale)

On Tue, 20 Aug 2024 08:57:07 +0200, Dmitry A. Kazakov wrote:

On 2024-08-20 01:03, Lawrence D'Oliveiro wrote:
>

On Mon, 19 Aug 2024 13:03:23 +0200, Dmitry A. Kazakov wrote:
 

Again. It is called overlapped I/O. You can start multiple
*asynchronous* I/O operations from a thread.

 
I’m not talking about using threads. I’m talking about avoiding
threads, and all their potential for difficult-to-fix race-condition
-type bugs.
 
I’m talking about situations where the bottleneck is the I/O, not the
CPU, so multithreading gets you nothing.

 
It seems you suffer some form of dyslexia. I clearly stated that all
instances of overlapped I/O is started from the same/single/one thread.
Better now?

Do I need to repeat that this has nothing to do with threading?