Vilya Harvey vilya.har...@gmail.com added the comment:
Petri: yes, that what I was suggesting.
Charles-François: I'm certainly open to alternatives. Unless I've overlooked
something though, the problem is that no workaround is possible at the moment.
BTW this came up in the context
New submission from Vilya Harvey vilya.har...@gmail.com:
The signal module is oblivious to any changes to the set of installed signal
handlers which occur outside of the module. This can happen when a native
module changes a signal handler, or when the python interpreter is embedded
Changes by Vilya Harvey vilya.har...@gmail.com:
--
title: signal module in ignores external signal changes - signal module
ignores external signal changes
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13285
Vilya Harvey vilya.har...@gmail.com added the comment:
Could it return an opaque wrapper object, rather than just the raw address?
Something like:
typedef struct _PyNativeSignalHandler {
PyObject_HEAD
sighandler_t handler_func;
} PyNativeSignalHandler;
where the type object doesn't expose
New submission from Vilya Harvey:
The page at http://docs.python.org/lib/about.html refers people to the
old SourceForge bug tracker, rather than bugs.python.org.
--
messages: 59707
nosy: vilya
severity: normal
status: open
title: The Library Reference still refers to the old bug
New submission from Vilya Harvey:
The page at 'http://docs.python.org/lib/serverproxy-objects.html'
contains the following text which should be removed as it's (a) not
especially relevant; and (b) out of date:
Introspection methods are currently supported by servers written in
PHP, C
