oren wrote: > Not before all all Python I/O calls are converted to be EINTR-safe. >=20 > After running into some problems with I/O interrupted by signals I = tried to > fix it myself but it requires a lot of work in some of the hairiest = places=20 > in the Python codebase. sounds like a good topic for a "here's what I learned when trying to fix this problem" PEP. </F>