Message 123957 - Python tracker

➜

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.

In-reply-to
Author	pitrou
Recipients	abo, astrand, benjamin.peterson, christian.heimes, collinwinter, djc, dsagal, exarkun, flox, giampaolo.rodola, gjb1002, gregory.p.smith, grossetti, jlamanna, jonash, jyasskin, kanaka, nnorwitz, oefe, pitrou, r.david.murray, santoni, shaphiro, siemer, tom_culliton, yonas
Date	2010年12月14日.15:58:57
SpamBayes Score	5.2927305e-08
Marked as misclassified	No
Message-id	<1292342349.39.0.540480361613.issue1731717@psf.upfronthosting.co.za>

Content
It seems the canonical spelling is SIGCHLD. SIGCLD doesn't exist everywhere and it produces test failures under OS X: http://www.python.org/dev/buildbot/all/builders/AMD64%20Leopard%203.x http://www.python.org/dev/buildbot/all/builders/AMD64%20Snow%20Leopard%203.x FWIW, this is what POSIX says: "Some implementations, including System V, have a signal named SIGCLD, which is similar to SIGCHLD in 4.2 BSD. POSIX.1 permits implementations to have a single signal with both names. POSIX.1 carefully specifies ways in which conforming applications can avoid the semantic differences between the two different implementations. The name SIGCHLD was chosen for POSIX.1 because most current application usages of it can remain unchanged in conforming applications. SIGCLD in System V has more cases of semantics that POSIX.1 does not specify, and thus applications using it are more likely to require changes in addition to the name change." http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xsh_chap02.html

Content

It seems the canonical spelling is SIGCHLD. SIGCLD doesn't exist everywhere and it produces test failures under OS X:
http://www.python.org/dev/buildbot/all/builders/AMD64%20Leopard%203.x
http://www.python.org/dev/buildbot/all/builders/AMD64%20Snow%20Leopard%203.x
FWIW, this is what POSIX says:
"Some implementations, including System V, have a signal named SIGCLD, which is similar to SIGCHLD in 4.2 BSD. POSIX.1 permits implementations to have a single signal with both names. POSIX.1 carefully specifies ways in which conforming applications can avoid the semantic differences between the two different implementations. The name SIGCHLD was chosen for POSIX.1 because most current application usages of it can remain unchanged in conforming applications. SIGCLD in System V has more cases of semantics that POSIX.1 does not specify, and thus applications using it are more likely to require changes in addition to the name change."
http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xsh_chap02.html

History
Date	User	Action	Args
2010年12月14日 15:59:09	pitrou	set	recipients: + pitrou, nnorwitz, collinwinter, abo, gregory.p.smith, astrand, siemer, exarkun, gjb1002, oefe, giampaolo.rodola, christian.heimes, dsagal, jyasskin, tom_culliton, benjamin.peterson, djc, grossetti, r.david.murray, yonas, jonash, flox, kanaka, santoni, shaphiro, jlamanna
2010年12月14日 15:59:09	pitrou	set	messageid: <1292342349.39.0.540480361613.issue1731717@psf.upfronthosting.co.za>
2010年12月14日 15:58:58	pitrou	link	issue1731717 messages
2010年12月14日 15:58:57	pitrou	create

homepage