This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients gvanrossum, loewis, neologix, pitrou, python-dev, vstinner, yselivanov
Date 2014-07-25.07:02:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Pipes cannot be configured in non-blocking mode on Windows. It sounds dangerous to call a blocking syscall in a signal handler.
> In fact, it works to write the signal number into a pipe on Windows, but I'm worried about the blocking behaviour.

OK, but if someone passes a socket in blocking mode, it will be accepted.
I don't understand why, if you're worried about a blocking write, you
don't just check that the FD passed is in non-blocking mode. It's
conceptually cleaner, more direct and safer.

Also, I think there's another issue open on the tracker to check just
that, so I'd leave this check out here.
Date User Action Args
2014-07-25 07:02:54neologixsetrecipients: + neologix, gvanrossum, loewis, pitrou, vstinner, python-dev, yselivanov
2014-07-25 07:02:54neologixlinkissue22018 messages
2014-07-25 07:02:54neologixcreate