➜

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 Casey Lucas
Recipients Casey Lucas, koobs
Date 2016-08-19.23:59:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471651195.23.0.67845273163.issue27808@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm not sure if this a Python issue or a FreeBSD issue but the return value from os.waitpid is not reliably (0,0) on FreeBSD when the WNOHANG is used and the child process has not yet exited.  Python docs say that the return value will be (0,0) but this is not the case.  I believe it is because the FreeBSD implementation of waitpid writes an uninitialized value to the status field when a child process is not available.  See also: http://stackoverflow.com/questions/38984449/is-status-value-from-os-waitpid-unreliable-when-os-wnohang-is-used-under-freebsd

Maybe this is just a documentation issue?  Or does the C code in the Python library need to handle this case?
History
Date User Action Args
2016-08-19 23:59:55Casey Lucassetrecipients: + Casey Lucas, koobs
2016-08-19 23:59:55Casey Lucassetmessageid: <1471651195.23.0.67845273163.issue27808@psf.upfronthosting.co.za>
2016-08-19 23:59:54Casey Lucaslinkissue27808 messages
2016-08-19 23:59:54Casey Lucascreate