On Mon, 19 Jul 2010 20:06:16 +0200, Antoine Pitrou wrote:
> So, in short, Python doesn't check SIGKILL by itself. It's just
> forbidden by the underlying C standard library,
Actually, it's forbidden by the kernel. The C library just passes along
the error to Python, which just passes it to the ap
Yes, yes, thank you both. That is exactly what I didn't understand, I knew
it was some how linked to the C library and wasn't exactly being handled or
decided at the Python layer, I just didn't understand the C part good
enough. I have found the CPython source code that checks. I see what you are
s
Hello,
> I am not asking about the signals, I understand them,
> I am asking about the registration of the SIGNAL handler and how it knows
> that you are trying to register SIGKILL, you get an error like this.
>
> ./signal-catcher.py
> Traceback (most recent call last):
> File "./signal-catch
On 07/19/2010 07:28 PM, Scott McCarty wrote:
> All, I just want to understand the C/Python piece better because I am
> writing a tutorial on signals and I am using python to demonstrate. I
> thought it would be fun to show that the SIGKILL is never processed, but
> instead python errors out. There
All, I just want to understand the C/Python piece better because I am
writing a tutorial on signals and I am using python to demonstrate. I
thought it would be fun to show that the SIGKILL is never processed, but
instead python errors out. There is something in Python checking the SIGKILL
signal h
