U e5d(@s|dZdZGdddZGdddeZGdddeZGdd d eeZGd d d eZGd d d eZGdddeZdS)zAbstract Transport class.) BaseTransport ReadTransportWriteTransport TransportDatagramTransportSubprocessTransportc@sHeZdZdZdZdddZdddZdd Zd d Zd d Z ddZ dS)rzBase class for transports._extraNcCs|dkr i}||_dSNr)selfextrar */usr/lib64/python3.8/asyncio/transports.py__init__szBaseTransport.__init__cCs|j||S)z#Get optional transport information.)rget)r namedefaultr r r get_extra_infoszBaseTransport.get_extra_infocCstdS)z2Return True if the transport is closing or closed.NNotImplementedErrorr r r r is_closingszBaseTransport.is_closingcCstdS)aClose the transport. Buffered data will be flushed asynchronously. No more data will be received. After all buffered data is flushed, the protocol's connection_lost() method will (eventually) be called with None as its argument. Nrrr r r closeszBaseTransport.closecCstdS)zSet a new protocol.Nr)r protocolr r r set_protocol%szBaseTransport.set_protocolcCstdS)zReturn the current protocol.Nrrr r r get_protocol)szBaseTransport.get_protocol)N)N) __name__ __module__ __qualname____doc__ __slots__rrrrrrr r r r r s   rc@s,eZdZdZdZddZddZddZd S) rz#Interface for read-only transports.r cCstdS)z*Return True if the transport is receiving.Nrrr r r is_reading3szReadTransport.is_readingcCstdS)zPause the receiving end. No data will be passed to the protocol's data_received() method until resume_reading() is called. Nrrr r r pause_reading7szReadTransport.pause_readingcCstdS)zResume the receiving end. Data received will once again be passed to the protocol's data_received() method. Nrrr r r resume_reading?szReadTransport.resume_readingN)rrrrrr r!r"r r r r r.s rc@sNeZdZdZdZdddZddZdd Zd d Zd d Z ddZ ddZ dS)rz$Interface for write-only transports.r NcCstdS)aSet the high- and low-water limits for write flow control. These two values control when to call the protocol's pause_writing() and resume_writing() methods. If specified, the low-water limit must be less than or equal to the high-water limit. Neither value can be negative. The defaults are implementation-specific. If only the high-water limit is given, the low-water limit defaults to an implementation-specific value less than or equal to the high-water limit. Setting high to zero forces low to zero as well, and causes pause_writing() to be called whenever the buffer becomes non-empty. Setting low to zero causes resume_writing() to be called only once the buffer is empty. Use of zero for either limit is generally sub-optimal as it reduces opportunities for doing I/O and computation concurrently. Nrr highlowr r r set_write_buffer_limitsMsz&WriteTransport.set_write_buffer_limitscCstdS)z,Return the current size of the write buffer.Nrrr r r get_write_buffer_sizebsz$WriteTransport.get_write_buffer_sizecCstdS)zWrite some data bytes to the transport. This does not block; it buffers the data and arranges for it to be sent out asynchronously. Nr)r datar r r writefszWriteTransport.writecCsd|}||dS)zWrite a list (or any iterable) of data bytes to the transport. The default implementation concatenates the arguments and calls write() on the result. N)joinr))r Z list_of_datar(r r r writelinesns zWriteTransport.writelinescCstdS)zClose the write end after flushing buffered data. (This is like typing ^D into a UNIX program reading from stdin.) Data may still be received. Nrrr r r write_eofwszWriteTransport.write_eofcCstdS)zAReturn True if this transport supports write_eof(), False if not.Nrrr r r can_write_eofszWriteTransport.can_write_eofcCstdSzClose the transport immediately. Buffered data will be lost. No more data will be received. The protocol's connection_lost() method will (eventually) be called with None as its argument. Nrrr r r abortszWriteTransport.abort)NN) rrrrrr&r'r)r,r-r.r0r r r r rHs   rc@seZdZdZdZdS)raSInterface representing a bidirectional transport. There may be several implementations, but typically, the user does not implement new transports; rather, the platform provides some useful transports that are implemented using the platform's best practices. The user never instantiates a transport directly; they call a utility function, passing it a protocol factory and other information necessary to create the transport and protocol. (E.g. EventLoop.create_connection() or EventLoop.create_server().) The utility function will asynchronously create a transport and a protocol and hook them up by calling the protocol's connection_made() method, passing it the transport. The implementation here raises NotImplemented for every method except writelines(), which calls write() in a loop. r N)rrrrrr r r r rsrc@s&eZdZdZdZdddZddZdS) rz(Interface for datagram (UDP) transports.r NcCstdS)aSend data to the transport. This does not block; it buffers the data and arranges for it to be sent out asynchronously. addr is target socket address. If addr is None use target address pointed on transport creation. Nr)r r(Zaddrr r r sendtoszDatagramTransport.sendtocCstdSr/rrr r r r0szDatagramTransport.abort)N)rrrrrr1r0r r r r rs rc@s@eZdZdZddZddZddZdd Zd d Zd d Z dS)rr cCstdS)zGet subprocess id.Nrrr r r get_pidszSubprocessTransport.get_pidcCstdS)zGet subprocess returncode. See also http://docs.python.org/3/library/subprocess#subprocess.Popen.returncode Nrrr r r get_returncodesz"SubprocessTransport.get_returncodecCstdS)z&Get transport for pipe with number fd.Nr)r fdr r r get_pipe_transportsz&SubprocessTransport.get_pipe_transportcCstdS)zSend signal to subprocess. See also: docs.python.org/3/library/subprocess#subprocess.Popen.send_signal Nr)r signalr r r send_signalszSubprocessTransport.send_signalcCstdS)aLStop the subprocess. Alias for close() method. On Posix OSs the method sends SIGTERM to the subprocess. On Windows the Win32 API function TerminateProcess() is called to stop the subprocess. See also: http://docs.python.org/3/library/subprocess#subprocess.Popen.terminate Nrrr r r terminates zSubprocessTransport.terminatecCstdS)zKill the subprocess. On Posix OSs the function sends SIGKILL to the subprocess. On Windows kill() is an alias for terminate(). See also: http://docs.python.org/3/library/subprocess#subprocess.Popen.kill Nrrr r r kills zSubprocessTransport.killN) rrrrr2r3r5r7r8r9r r r r rsrcsZeZdZdZdZdfdd ZddZdd Zd d Zdd d Z dddZ ddZ Z S)_FlowControlMixinavAll the logic for (write) flow control in a mix-in base class. The subclass must implement get_write_buffer_size(). It must call _maybe_pause_protocol() whenever the write buffer size increases, and _maybe_resume_protocol() whenever it decreases. It may also override set_write_buffer_limits() (e.g. to specify different defaults). The subclass constructor must call super().__init__(extra). This will call set_write_buffer_limits(). The user may call set_write_buffer_limits() and get_write_buffer_size(), and their protocol's pause_writing() and resume_writing() may be called. )_loop_protocol_paused _high_water _low_waterNcs0t||dk st||_d|_|dS)NF)superrAssertionErrorr;r<_set_write_buffer_limits)r r Zloop __class__r r rs   z_FlowControlMixin.__init__c Cs|}||jkrdS|jsd|_z|jWnRttfk rJYn:tk r}z|j d|||jdW5d}~XYnXdS)NTzprotocol.pause_writing() failedmessageZ exceptionZ transportr) r'r=r< _protocolZ pause_writing SystemExitKeyboardInterrupt BaseExceptionr;call_exception_handler)r sizeexcr r r _maybe_pause_protocols  z'_FlowControlMixin._maybe_pause_protocolc Cs|jr|||jkr|d|_z|jWnRttfk rBYn:tk rz}z|j d|||jdW5d}~XYnXdS)NFz protocol.resume_writing() failedrD) r<r'r>rFZresume_writingrGrHrIr;rJ)r rLr r r _maybe_resume_protocol!s z(_FlowControlMixin._maybe_resume_protocolcCs |j|jfSr )r>r=rr r r get_write_buffer_limits1sz)_FlowControlMixin.get_write_buffer_limitscCsj|dkr|dkrd}nd|}|dkr.|d}||krBdksZntd|d|d||_||_dS)Nizhigh (z) must be >= low (z) must be >= 0) ValueErrorr=r>r#r r r rA4sz*_FlowControlMixin._set_write_buffer_limitscCs|j||d|dS)N)r$r%)rArMr#r r r r&Dsz)_FlowControlMixin.set_write_buffer_limitscCstdSr rrr r r r'Hsz'_FlowControlMixin.get_write_buffer_size)NN)NN)NN) rrrrrrrMrNrOrAr&r' __classcell__r r rBr r:s  r:N) r__all__rrrrrrr:r r r r s%F6