| Server IP : 121.121.20.254 / Your IP : 216.73.216.202 Web Server : Microsoft-IIS/10.0 System : Windows NT WEB-SERVER 10.0 build 20348 (Windows Server 2022) AMD64 User : IUSR ( 0) PHP Version : 8.3.28 Disable Function : NONE MySQL : ON | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : C:/Python315/Lib/test/__pycache__/ |
Upload File : |
R
>lqj} c � � Q s ] PHs] PHs] PHs] PHs] QHGs ] QHGs ] PH$s ]s
Qs]s Q Q\O 2 sP! )ar 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.
)�support)�threading_helperg �?c �@ ` � \ sQ s]s n Q sQ sQ sQ sQ sQs U s
P! )�ForkWaitc �f � [ O 2 U m - U m ] U m , U m P! )� )r �threading_setup�_threading_key�alive�stop�threads)�selfs &�#C:\Python315\\Lib\test\fork_wait.py�setUp�ForkWait.setUp s( � �.�>�>�@�����
��� ���� c �� � ]U m U O F D oUO 2 J PoU O O 2 [ O
U O P! )� )r
r �join�clearr �threading_cleanupr )r �threads & r
�tearDown�ForkWait.tearDown sI � ��� ��l�l�F��K�K�M� #����������*�*�D�,?�,?�@r c �� � U O % f@ [ O 2 U O U$ [ O
[ 2 JQ P! [ c Ja h 9 h)N)r
�os�getpidr �time�sleep�
SHORTSLEEP�OSError)r �ids &&r
�f�
ForkWait.f( sH � ��)�)�)��Y�Y�[�D�J�J�r�N�
��
�
�:�&� �� �
��
�s �A � A$�A$�#A$c �6 � [ O VQ 5 P! )��exitcode)r �wait_process)r �cpidr% s &&$r
� wait_impl�ForkWait.wait_impl0 s � ����T�5r c � � [ [ 2 F DQ o[ O U O U1Q 5 oUO 2 U O O U2 JS [ O [ O 2 F D$ o[ U O 2 [ 6� f J# L [ U O O 2 2 oU O U[! [ [ 2 2 2 U O O# 2 o[$ O&