U
|
Z ±d
|
ã @ sB d dl Z d dlZd dlZddlmZ ddlmZ G dd dZdS )é Né )Ú_core)Úis_main_threadc @ s< e Zd Zdd Zdd Zdd Zdd Zd d
|
Zd d Zd S )ÚWakeupSocketpairc C s t ¡ \| _| _| j d¡ | j d¡ | j t jt jd¡ | j t jt jd¡ z| j t j t j
|
d¡ W n t k
|
r| Y nX d | _ d S )NFé ) ÚsocketÚ
|
socketpairÚ wakeup_sockÚ
|
write_sockÚ setblockingÚ
|
setsockoptÚ
|
SOL_SOCKETÚ SO_RCVBUFÚ SO_SNDBUFÚ IPPROTO_TCPÚ TCP_NODELAYÚOSErrorÚ old_wakeup_fd©Úself© r úTd:\z\workplace\vscode\pyvenv\venv\Lib\site-packages\trio/_core/_wakeup_socketpair.pyÚ__init__
|
s zWakeupSocketpair.__init__c C s* z| j d¡ W n tk
|
r$ Y nX d S )Nó )r
|
ÚsendÚBlockingIOErrorr r r r Ú wakeup_thread_and_signal_safe s z.WakeupSocketpair.wakeup_thread_and_signal_safec à s t | j¡I d H | ¡ d S ©N)r Z wait_readabler Údrainr r r r Ú
|
wait_woken& s zWakeupSocketpair.wait_wokenc C s, z| j d¡ qW n tk
|
r& Y nX d S )Ni )r Úrecvr r r r r r * s zWakeupSocketpair.drainc C sN | j d kstt sd S | j ¡ }tj|dd| _ | j dkrJt t d¡ d S )NF)Zwarn_on_full_bufferéÿÿÿÿa It looks like Trio's signal handling code might have collided with another library you're using. If you're running Trio in guest mode, then this might mean you should set host_uses_signal_set_wakeup_fd=True. Otherwise, file a bug on Trio and we'll help you figure out what's going on.)
|
r ÚAssertionErrorr r
|
ÚfilenoÚsignalÚ set_wakeup_fdÚwarningsÚwarnÚRuntimeWarning)r Úfdr r r Úwakeup_on_signals1 s
|
|
ÿÿz"WakeupSocketpair.wakeup_on_signalsc C s. | j ¡ | j ¡ | jd k r*t | j¡ d S r )r Úcloser
|
r r$ r% r r r r r+ C s
|
|
|
zWakeupSocketpair.closeN) Ú__name__Ú
|
__module__Ú __qualname__r r r r r* r+ r r r r r s r )r r$ r& Ú r Z_utilr r r r r r Ú<module> s
|
|
