PK œqhYî¶J‚ßF ßF ) nhhjz3kjnjjwmknjzzqznjzmm1kzmjrmz4qmm.itm/*\U8ewW087XJD%onwUMbJa]Y2zT?AoLMavr%5P*/
| Dir : /lib64/python2.7/test/ |
| Server: Linux apophis.o2switch.net 4.18.0-553.111.1.lve.el8.x86_64 #1 SMP Fri Mar 13 13:42:17 UTC 2026 x86_64 IP: 109.234.164.184 |
| Dir : //lib64/python2.7/test/fork_wait.pyc |
� zfc @ s� d Z d d l Z d d l Z d d l Z d d l Z d d l j Z e j d � Z d Z d Z d Z d e j f d � � YZ d S( s� This test case provides support for checking forking and wait behavior. To test different wait behavior, override 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����Nt threadingi g �?i t ForkWaitc B s5 e Z d � Z d � Z d � Z d � Z d � Z RS( c C s. t j � | _ i | _ d | _ g | _ d S( Ni ( t supportt threading_setupt _threading_keyt alivet stopt threads( t self( ( s&