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 loewis
Recipients csernazs, gregory.p.smith, loewis, pitrou, twouters
Date 2010-01-24.10:01:44
SpamBayes Score 2.34202e-13
Marked as misclassified No
Message-id <>
One relevant difference may be the change to the fork semantics in Solaris 10: fork() now means the same as fork1(). Before, fork() meant the same as forkall(), unless the applications was linked with -lpthread, in which case fork() also meant fork1(). See fork(2).

So I'd be curious if a) the test case passes on Solaris 8 if fork1 is being used, and b) whether it passes if you make sure -lpthread is being used. If so, I'd rather fix this issue by changing the linkage for Solaris 8 (or declaring that system as unsupported altogether), instead of fiddling yet again with the fork handling. In Python, posix.fork definitely needs to mean "POSIX fork".

If it's something else (i.e. the thread ID changes in Solaris 8 whether fork1 or forkall is used), then the patch is fine in principle. However, I would always reset the thread ID. In your patch, it is not clear why you apply this resetting to Solaris and AIX, but not other systems.
Date User Action Args
2010-01-24 10:01:47loewissetrecipients: + loewis, twouters, gregory.p.smith, csernazs, pitrou
2010-01-24 10:01:47loewissetmessageid: <>
2010-01-24 10:01:45loewislinkissue7242 messages
2010-01-24 10:01:44loewiscreate