| Server IP : 3.111.61.48 / Your IP : 216.73.216.67 Web Server : Apache System : Linux ip-10-0-5-176 6.8.0-1057-aws #60~22.04.1-Ubuntu SMP Wed May 27 08:16:59 UTC 2026 x86_64 User : ubuntu ( 1000) PHP Version : 8.2.31 Disable Function : exec,passthru,shell_exec,system MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/lib/python3.10/test/__pycache__/ |
Upload File : |
o
�9j� � @ sf d Z ddlZddlZddlZddlZddlZddlmZ ddlm Z dZ
dZdZG dd � d ej
�ZdS )
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.
� N)�support)�threading_helper� g �?� c @ s4 e Zd Zdd� Zdd� Zdd� Zdd� Zd d
� ZdS )�ForkWaitc C s t �� | _i | _d| _g | _d S )Nr )r �threading_setup�_threading_key�alive�stop�threads)�self� r
�%/usr/lib/python3.10/test/fork_wait.py�setUp s
zForkWait.setUpc C s8 d| _ | jD ]}|�� qd }| j�� tj| j� d S )N� )r
r �join�clearr �threading_cleanupr )r �threadr
r
r �tearDown s
zForkWait.tearDownc C sD | j s t�� | j|<