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 rstutsman
Recipients ajaksu2, christian.heimes, loewis, rstutsman, stutsman
Date 2009-05-18.23:17:45
SpamBayes Score 7.477059e-10
Marked as misclassified No
Message-id <1242688667.42.0.0637009018055.issue1983@psf.upfronthosting.co.za>
In-reply-to
Content
No, I don't think this is actually fixed in any version of Python at the
moment.  The title may be a bit misleading, because all the versions now
store the result of fork in a pid_t and return it as a PyLong.  However,
posix_waitpid is still pulling pid's as a PyInt.  Changing this to
PyLong would probably work for our purposes, but I guess the hangup was
that in reality pid_t is supposed to be an opaque datatype and
implementing it in CPython is non-trivial and has little benefit.

Perhaps we close this as won't fix or I can create a patch to at least
give a hack for 64-bit pid's but still treated as a long.
History
Date User Action Args
2009-05-18 23:17:47rstutsmansetrecipients: + rstutsman, loewis, christian.heimes, ajaksu2, stutsman
2009-05-18 23:17:47rstutsmansetmessageid: <1242688667.42.0.0637009018055.issue1983@psf.upfronthosting.co.za>
2009-05-18 23:17:46rstutsmanlinkissue1983 messages
2009-05-18 23:17:45rstutsmancreate