a (j9!@sUddlmZddlZddlZddlZddlmZddlZddlm Z ddl m Z m Z erfddlm ZerxejdksxJd Zd ed <Gd d d Ze Gddde ZdS)) annotationsN) TYPE_CHECKING)Stream)ConflictDetectorfinal)Finalwin32i FinalTypeDEFAULT_RECEIVE_SIZEc@sbeZdZUded<dddddZeddd d Zddd d Zddd dZddddZ dS) _FdHolderintfdNonerreturncCs:d|_t|tstd||_t||_t|ddS)Nzfile descriptor must be an intF)r isinstancer TypeErrorosZ get_blocking_original_is_blocking set_blockingselfrr6E:\soccer\ml_env\Lib\site-packages\trio/_unix_pipes.py__init__+s   z_FdHolder.__init__boolrcCs |jdkSNr)rrrrrclosed6sz_FdHolder.closedcCs2|jr dS|j}d|_t||jt|dSr)r!rrrrcloserrrr _raw_close:s z_FdHolder._raw_closecCs |dSN)r#r rrr__del__Isz_FdHolder.__del__cCs |jstj|j|dSr$)r!triolowlevelZnotify_closingrr#r rrrr"Lsz_FdHolder.closeN) __name__ __module__ __qualname____annotations__rpropertyr!r#r%r"rrrrr s  r c@szeZdZdZdddddZdddd d Zdd d d ZddddddZdd ddZdd ddZ dd ddZ dS)FdStreamaRepresents a stream given the file descriptor to a pipe, TTY, etc. *fd* must refer to a file that is open for reading and/or writing and supports non-blocking I/O (pipes and TTYs will work, on-disk files probably not). The returned stream takes ownership of the fd, so closing the stream will close the fd too. As with `os.fdopen`, you should not directly use an fd after you have wrapped it in a stream using this function. To be used as a Trio stream, an open file must be placed in non-blocking mode. Unfortunately, this impacts all I/O that goes through the underlying open file, including I/O that uses a different file descriptor than the one that was passed to Trio. If other threads or processes are using file descriptors that are related through `os.dup` or inheritance across `os.fork` to the one that Trio is using, they are unlikely to be prepared to have non-blocking I/O semantics suddenly thrust upon them. For example, you can use ``FdStream(os.dup(sys.stdin.fileno()))`` to obtain a stream for reading from standard input, but it is only safe to do so with heavy caveats: your stdin must not be shared by any other processes, and you must not make any calls to synchronous methods of `sys.stdin` until the stream returned by `FdStream` is closed. See `issue #174 `__ for a discussion of the challenges involved in relaxing this restriction. .. warning:: one specific consequence of non-blocking mode applying to the entire open file description is that when your program is run with multiple standard streams connected to a TTY (as in a terminal emulator), all of the streams become non-blocking when you construct an `FdStream` for any of them. For example, if you construct an `FdStream` for standard input, you might observe Python loggers begin to fail with `BlockingIOError`. Args: fd (int): The fd to be wrapped. Returns: A new `FdStream` object. r rrcCs"t||_td|_td|_dS)Nz*another task is using this stream for sendz-another task is using this stream for receive)r _fd_holderr_send_conflict_detector_receive_conflict_detectorrrrrr|s zFdStream.__init__bytes)datarc sB|j$|jjrtdtjIdHt|}t|}d}||kr||d}z|t |jj |7}Wnlt ytj |jj IdHYnFty}z.|jtjkrtddntj|WYd}~n d}~00WdqB1s0YqBWdn1s0YWdn1s40YdS)Nfile was already closedr)r/r.r!r&ClosedResourceErrorr' checkpointlen memoryviewrwriterBlockingIOError wait_writableOSErrorerrnoEBADFBrokenResourceError)rr2lengthviewsent remainingerrrsend_alls*     zFdStream.send_allrc s|jj|jjrtdztj|jjIdHWn,ty`}ztj |WYd}~n d}~00Wdn1sv0YdS)Nr3) r/r.r!r&r4r'r:rBrokenPipeErrorr>)rrCrrrwait_send_all_might_not_blocks z&FdStream.wait_send_all_might_not_blockNz int | None) max_bytesrc s|j|durt}n"t|ts(td|dkr8tdtjIdHzt |j j |}Wqt ytj|j j IdHYqHty}z.|jtjkrtddntj|WYd}~qHd}~00qqH|WdS1s0YdS)Nzmax_bytes must be integer >= 1rr3)r0r rr r ValueErrorr&r'r5rreadr.rr9Z wait_readabler;r<r=r4r>)rrGr2excrrr receive_somes,   zFdStream.receive_somecCs|jdSr$)r.r"r rrrr"szFdStream.closecs|tjIdHdSr$)r"r&r'r5r rrracloseszFdStream.aclosecCs|jjSr$)r.rr rrrfilenoszFdStream.fileno)N) r(r)r*__doc__rrDrFrKr"rLrMrrrrr-Rs(  r-) __future__rr<rsystypingrr&_abcrZ_utilrrrr platformr r+r r-rrrrs    ;