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 neologix, skrah, vstinner
Date 2011-10-01.10:19:04
SpamBayes Score 0.01707537
Marked as misclassified No
Message-id <1317464345.91.0.210701626116.issue13084@psf.upfronthosting.co.za>
In-reply-to
Content
See http://bugs.python.org/issue12469, specifically http://bugs.python.org/issue12469#msg139831

"""
> > 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.
"""

Looks like we now have a failure :-)
History
Date User Action Args
2011-10-01 10:19:06neologixsetrecipients: + neologix, vstinner, skrah
2011-10-01 10:19:05neologixsetmessageid: <1317464345.91.0.210701626116.issue13084@psf.upfronthosting.co.za>
2011-10-01 10:19:05neologixlinkissue13084 messages
2011-10-01 10:19:04neologixcreate