Ñò à"Ic@sqdZddkZddkZddkZddkZddkZdZdZdZdei fd„ƒYZ dS(sûThis test case provides support for checking forking and wait behavior. To test different wait behavior, overrise the wait_impl method. We want fork1() semantics -- only the forking thread survives in the child after a fork(). On some systems (e.g. Solaris without posix threads) we find that all active threads survive in the child after a fork(); this is an error. While BeOS doesn't officially support fork and native threading in the same application, the present example should work just fine. DC iÿÿÿÿNigà?itForkWaitcBs,eZd„Zd„Zd„Zd„ZRS(cCsh|_d|_dS(Ni(talivetstop(tself((s+/mit/python/lib/python2.6/test/fork_wait.pytsetUps cCsPxI|ip>tiƒ|i| s <