➜

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 vstinner
Recipients loewis, neologix, python-dev, vstinner
Date 2011-07-05.08:05:14
SpamBayes Score 0.00090526394
Marked as misclassified No
Message-id <1309853116.2491.2.camel@marge>
In-reply-to <CAH_1eM1Qa5nhxVa8fdnTvHB8eRyuD5xetWum_swpTs26Xx+i-w@mail.gmail.com>
Content 
> > When signals are unblocked, pending signal ared delivered in the reverse order
> > of their number (also on Linux, not only on FreeBSD 6).
> 
> I don't like this.
> POSIX doesn't make any guarantee about signal delivery order, except
> for real-time signals.
> It might work on FreeBSD and Linux, but that's definitely not
> documented, and might break with new kernel releases, or other
> kernels.

It looks like it works like this on most OSes (Linux, Mac OS X, Solaris,
FreeBSD): I don't see any test_signal failure on 3.x buildbots. If we
have a failure, we can use set() again, but only for test_pending:
signal order should be reliable if signals are not blocked.
History
Date User Action Args
2011-07-05 08:05:15vstinnersetrecipients: + vstinner, loewis, neologix, python-dev
2011-07-05 08:05:14vstinnerlinkissue12469 messages
2011-07-05 08:05:14vstinnercreate