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 David.Edelsohn, gvanrossum, neologix, python-dev, skrah
Date 2013-10-19.18:03:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1C4F0JFPPGbbAQoaLmzNV+7bvYr0CXKiSWKs7=oL9qOQ@mail.gmail.com>
In-reply-to <1382204860.26.0.984115339096.issue19293@psf.upfronthosting.co.za>
Content
Wait, I think there's a misunderstanding here.
POSIX does indeed leave undefined the behavior of syscalls when a
signal is received: whether or not it fails with EINTR depends on the
operating system, the SA_RESTART flag, etc.

But the tests we're talking about send signals whose default actions
are to terminate the process (e.g. SIGTERM, SIGHUP, etc): I cannot
beleive AIX doesn't terminate the processes in these situations, I
think it's a bug in asyncio which prevent the termination from being
detected (David, you can just use "ps" to check that the processes are
indeed terminated).
History
Date User Action Args
2013-10-19 18:03:28neologixsetrecipients: + neologix, gvanrossum, skrah, python-dev, David.Edelsohn
2013-10-19 18:03:28neologixlinkissue19293 messages
2013-10-19 18:03:27neologixcreate