mirror of https://github.com/python/cpython
cosmetics
This commit is contained in:
parent
b9418686ba
commit
a3c04b003f
|
@ -264,7 +264,10 @@ rotor rotormodule.c # enigma-inspired encryption
|
|||
#sybase sybasemodule.c
|
||||
|
||||
|
||||
# Generic (SunOS / SVR4) dynamic loading module
|
||||
# Generic (SunOS / SVR4) dynamic loading module.
|
||||
# This is not needed for dynamic loading of Python modules --
|
||||
# it is a highly experimental and dangerous device for calling
|
||||
# *arbitrary* C functions in *arbitrary* shared libraries.
|
||||
|
||||
#dl dlmodule.c
|
||||
|
||||
|
|
|
@ -2,7 +2,6 @@
|
|||
*/
|
||||
|
||||
#include "allobjects.h"
|
||||
#include "modsupport.h"
|
||||
|
||||
#include <sys/types.h>
|
||||
|
||||
|
|
|
@ -57,7 +57,7 @@ OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
|||
generated by the keyboard (e.g. SIGINT) are delivered to all
|
||||
threads (e.g. SGI), while in others (e.g. Solaris) such signals are
|
||||
delivered to one random thread (an intermediate possibility would
|
||||
be to deliver it to the main thread -- POSIX???). For now, we have
|
||||
be to deliver it to the main thread -- POSIX?). For now, we have
|
||||
a working implementation that works in all three cases -- the
|
||||
handler ignores signals if getpid() isn't the same as in the main
|
||||
thread. XXX This is a hack.
|
||||
|
|
Loading…
Reference in New Issue