config root man

Current Path : /compat/linux/proc/self/root/usr/local/lib/python2.5/test/

FreeBSD hs32.drive.ne.jp 9.1-RELEASE FreeBSD 9.1-RELEASE #1: Wed Jan 14 12:18:08 JST 2015 root@hs32.drive.ne.jp:/sys/amd64/compile/hs32 amd64
Upload File :
Current File : //compat/linux/proc/self/root/usr/local/lib/python2.5/test/fork_wait.pyo

³ò
h”Rc	@sdZddkZddkZddkZddkZddkZddklZdZdZ	dZ
deifd„ƒ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ÿÿÿÿN(tTestSkippedigà?itForkWaitcBs,eZd„Zd„Zd„Zd„ZRS(cCsh|_d|_dS(Ni(talivetstop(tself((s*/usr/local/lib/python2.5/test/fork_wait.pytsetUps	cCsPxI|ip>tiƒ|i|<ytitƒWqtj
oqXqWdS(N(RtostgetpidRttimetsleept
SHORTSLEEPtIOError(Rtid((s*/usr/local/lib/python2.5/test/fork_wait.pytfs
c	CsŽxRtdƒD]D}ti|tiƒ\}}||joPntidtƒq
W|i||ƒ|i|dd|d@|d?fƒdS(Ni
iiscause = %d, exit = %diÿi(trangeRtwaitpidtWNOHANGRR	R
tassertEquals(Rtcpidtitspidtstatus((s*/usr/local/lib/python2.5/test/fork_wait.pyt	wait_impl$s

cCs:x*ttƒD]}ti|i|fƒq
Wtitƒ|ii	ƒ}|i
ƒ|i|ttƒƒ|iiƒ}t
idjotiƒ}n
tiƒ}|djo^titƒd}x7|iD],}|i|||jo|d7}qÎqÎWti|ƒn(|i|ƒd|_tidtƒdS(Nt	unixware7iii(R(RtNUM_THREADStthreadt	start_newR
RR	t	LONGSLEEPRtkeystsortRtcopytsystplatformRtfork1tforkt_exitRRR
(RRtat
prefork_livesRtntkey((s*/usr/local/lib/python2.5/test/fork_wait.pyt	test_wait0s,






	(t__name__t
__module__RR
RR((((s*/usr/local/lib/python2.5/test/fork_wait.pyRs			(
t__doc__RRRRtunittestttest.test_supportRRR
RtTestCaseR(((s*/usr/local/lib/python2.5/test/fork_wait.pys<module>
s<

Man Man