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 gvanrossum
Recipients giampaolo.rodola, gvanrossum, pitrou, python-dev, vstinner, yselivanov
Date 2014-07-17.17:43:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJJnb4AUa-YOEejXNZSo+Fp-xUPDh8c4z57Y1W+R7rR6mA@mail.gmail.com>
In-reply-to <1405613849.63.0.0136901015498.issue21645@psf.upfronthosting.co.za>
Content
The more esoteric system calls you use the more you end up debugging it on
esoteric platforms. :-(

On Thu, Jul 17, 2014 at 9:17 AM, STINNER Victor <report@bugs.python.org>
wrote:

>
> STINNER Victor added the comment:
>
> > I don't know if it can be useful, but there is also the
> signal.pthread_sigmask() which can be used to "queue" pending signals. (...)
>
> Oh, I didn't remember that I opened the issue #12060 to discuss "real time
> signals". The summary is that the wakeup fd should be used... Which is nice
> because it is the choice made by asyncio ;-)
>
> FYI I also opened the issue #21998: "asyncio: a new self-pipe should be
> created in the child process after fork" which is somehow related to this
> issue.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue21645>
> _______________________________________
>
History
Date User Action Args
2014-07-17 17:43:34gvanrossumsetrecipients: + gvanrossum, pitrou, vstinner, giampaolo.rodola, python-dev, yselivanov
2014-07-17 17:43:34gvanrossumlinkissue21645 messages
2014-07-17 17:43:34gvanrossumcreate