Message223924
| 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 | <CAH_1eM0nNo3LzxZaxTYFM-=Sn+2G+od4HjSYmnhzN1K-SZqUgA@mail.gmail.com> |
|---|
| In-reply-to | <1406235187.52.0.451160154281.issue22018@psf.upfronthosting.co.za> |
|---|
| Content |
|---|
> 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, youdon't just check that the FD passed is in non-blocking mode. It'sconceptually cleaner, more direct and safer.Also, I think there's another issue open on the tracker to check justthat, so I'd leave this check out here. |
|