ї <1DMґВ│ЭЦСр≈dZdZGd└dі╚ZGd└deі╚ZGd└deі╚ZGd└d eeі╚ZGd └deі╚ZGd└d eі╚ZGd└deі╚ZdS)zAbstract Transport class.)з BaseTransportз ReadTransportзWriteTransportз TransportзDatagramTransportзSubprocessTransportcС>≈eZdZdZdZd d└Zd d└Zd└Zd└Zd└Z d └Z dS)rzBase class for transports.╘з_extraNcС≈|─i}||_dS╘Nr )зselfзextras З9/opt/alt/python311/lib64/python3.11/asyncio/transports.pyз__init__zBaseTransport.__init__s─ь┬=ь┬Eь┬▄┬┬СcС8≈|j═||і╚S)z#Get optional transport information.)r зget)r зnameзdefaults rзget_extra_infozBaseTransport.get_extra_infos─Ю▄{▐┼≤t═Wя-т-п-rcС≈t┌)z2Return True if the transport is closing or closed.╘зNotImplementedError╘r s rз is_closingzBaseTransport.is_closingС─Е!п!rcС≈t┌)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. rrs rзclosezBaseTransport.closeС ─У"п!rcС≈t┌)zSet a new protocol.r)r зprotocols rзset_protocolzBaseTransport.set_protocol%rrcС≈t┌)zReturn the current protocol.rrs rзget_protocolzBaseTransport.get_protocol)rrr)з__name__з __module__з__qualname__з__doc__з __slots__rrrrr"r$╘rrrr s┐─────ь$п$Ю─IППППП .П.П.П.П"П"П"П"П"П"П"П"П"П"П"П"П"П"rrcС(≈eZdZdZdZd└Zd└Zd└ZdS)rz#Interface for read-only transports.r*cС≈t┌)z*Return True if the transport is receiving.rrs rз is_readingzReadTransport.is_reading3rrcС≈t┌)z■Pause the receiving end. No data will be passed to the protocol's data_received() method until resume_reading() is called. rrs rз pause_readingzReadTransport.pause_reading7С ─У"п!rcС≈t┌)z┘Resume the receiving end. Data received will once again be passed to the protocol's data_received() method. rrs rзresume_readingzReadTransport.resume_reading?r0rN)r%r&r'r(r)r-r/r2r*rrrr.sL─────ь-п-Ю─IП"П"П"П"П"П"П"П"П"П"П"rrcСH≈eZdZdZdZdd└Zd└Zd└Zd└Zd└Z d └Z d └Zd└ZdS) rz$Interface for write-only transports.r*NcС≈t┌)aіSet 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. r╘r зhighзlows rзset_write_buffer_limitsz&WriteTransport.set_write_buffer_limitsMs ─У&"п!rcС≈t┌)z,Return the current size of the write buffer.rrs rзget_write_buffer_sizez$WriteTransport.get_write_buffer_sizebrrcС≈t┌)z⌠Get the high and low watermarks for write flow control. Return a tuple (low, high) where low and high are positive number of bytes.rrs rзget_write_buffer_limitsz&WriteTransport.get_write_buffer_limitsfs ─У"п!rcС≈t┌)z²Write some data bytes to the transport. This does not block; it buffers the data and arranges for it to be sent out asynchronously. r)r зdatas rзwritezWriteTransport.writelr0rcСZ≈d═|і╚}|═|і╚dS)z╞Write a list (or any iterable) of data bytes to the transport. The default implementation concatenates the arguments and calls write() on the result. rN)зjoinr?)r зlist_of_datar>s rз writelineszWriteTransport.writelinests-─П▐x┼x≤я%т%┬ь▐ ┼ ░4ятпппrcС≈t┌)z╘Close the write end after flushing buffered data. (This is like typing ^D into a UNIX program reading from stdin.) Data may still be received. rrs rз write_eofzWriteTransport.write_eof}С ─У"п!rcС≈t┌)zAReturn True if this transport supports write_eof(), False if not.rrs rз can_write_eofzWriteTransport.can_write_eof├rrcС≈t┌╘zщClose 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. rrs rзabortzWriteTransport.abort┼rFr╘NN) r%r&r'r(r)r8r:r<r?rCrErHrKr*rrrrHs°─────ь.п.Ю─IП"П"П"П"П*"П"П"П"П"П"П"П"П"ПППП"П"П"П"П"П"П"П"П"П"П"rrcС≈eZdZdZdZdS)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)r%r&r'r(r)r*rrrr■s─────ППП(─I─I─IrrcС$≈eZdZdZdZdd└Zd└ZdS)rz(Interface for datagram (UDP) transports.r*NcС≈t┌)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. r)r r>зaddrs rзsendtozDatagramTransport.sendto╠rrcС≈t┌rJrrs rrKzDatagramTransport.abort╩rFrr)r%r&r'r(r)rQrKr*rrrr╛sB─────ь2п2Ю─IП"П"П"П"П"П"П"П"П"rrcС6≈eZdZdZd└Zd└Zd└Zd└Zd└Zd└Z dS) rr*cС≈t┌)zGet subprocess id.rrs rзget_pidzSubprocessTransport.get_pidиrrcС≈t┌)z┘Get subprocess returncode. See also http://docs.python.org/3/library/subprocess#subprocess.Popen.returncode rrs rзget_returncodez"SubprocessTransport.get_returncodeмr0rcС≈t┌)z&Get transport for pipe with number fd.r)r зfds rзget_pipe_transportz&SubprocessTransport.get_pipe_transportуrrcС≈t┌)z─Send signal to subprocess. See also: docs.python.org/3/library/subprocess#subprocess.Popen.send_signal r)r зsignals rзsend_signalzSubprocessTransport.send_signalыr0rcС≈t┌)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 rrs rз terminatezSubprocessTransport.terminateАs ─У"п!rcС≈t┌)zУKill 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 rrs rзkillzSubprocessTransport.killОs ─У"п!rN) r%r&r'r)rUrWrZr]r_rar*rrrrеss─────Ю─IП"П"П"П"П"П"П"П"П"П"П"П"П"П"П"П "П "П "П "П "rrcСP┤≈eZdZdZdZd┬fd└ Zd└Zd└Zd└Zdd└Z dd └Z d └Z┬xZS)з_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_waterNcС√∙≈tі╚═|і╚|─J┌||_d|_|═і╚dS)NF)зsuperrrdreз_set_write_buffer_limits)r rзloopз __class__s ─rrz_FlowControlMixin.__init__sNЬ─щ ┴▄вр≤ятпьпппь┬▄ ь %┬тьв%р%я'т'п'п'п'rcС6≈|═і╚}||jkrdS|jspd|_ |j═і╚dS#t tf$r┌t$r/}|j═ d|||jd°і╚Yd}~dSd}~wwxYwdS)NTzprotocol.pause_writing() failed╘зmessageз exceptionз transportr!) r:rfreз _protocolз pause_writingз SystemExitзKeyboardInterruptз BaseExceptionrdзcall_exception_handler)r зsizeзexcs rз_maybe_pause_protocolz'_FlowControlMixin._maybe_pause_protocolsЛ─ьв)р)я+т+┬ь░4т#р#п#ь┬Fьт$П ь$(┬Dт!П ь■в,р,я.т.п.п.п.Ьщу 1п2П П П ьщ П П П ь■ в1р1ь@ь!$ь!%ь $єП 3П3ЯТПППППППЬЬЬЬП ЬЬЬП П s╠AаBа'$BбBcС2≈|jr█|═і╚|jkrrd|_ |j═і╚dS#t tf$r┌t$r/}|j═ d|||jd°і╚Yd}~dSd}~wwxYwdSdS)NFz protocol.resume_writing() failedrn) rer:rgrrзresume_writingrtrurvrdrw)r rys rз_maybe_resume_protocolz(_FlowControlMixin._maybe_resume_protocol'sГ─ьт!П ьв*р*я,т,╟Єр?п?ь$)┬Dт!П ь■в-р-я/т/п/п/п/Ьщу 1п2П П П ьщ П П П ь■ в1р1ьAь!$ь!%ь $єП 3П3ЯТПППППППЬЬЬЬП ЬЬЬП П ь?п?sґAаBа#$B б BcС≈|j|jfSr)rgrfrs rr<z)_FlowControlMixin.get_write_buffer_limits7s─ь■═т!1п2п2rcС▓≈|─ |─d}nd|z}|─|dz}||cxkrdksntd|⌡d|⌡d²і╚┌||_||_dS)NiИИzhigh (z) must be >= low (z) must be >= 0)з ValueErrorrfrgr5s rrjz*_FlowControlMixin._set_write_buffer_limits:s┴─ь┬<ь┬{ь ░░Ю≤3▒w░ь┬;ь≤!▒)┬CЮ░sппрп≤aрпппщьH≤пHпH╟3пHпHпHЯJТJП JП ┬ть┬▄┬┬rcС\≈|═||╛і╚|═і╚dS)N)r6r7)rjrzr5s rr8z)_FlowControlMixin.set_write_buffer_limitsJs3─ьв%р%╗4╟Sп%я9т9п9ьв"р"я$т$п$п$п$rcС≈t┌rrrs rr:z'_FlowControlMixin.get_write_buffer_sizeNs─щ!п!rrL) r%r&r'r(r)rrzr}r<rjr8r:з __classcell__)rls@rrcrcШsЁЬ─────ППП K─IП(П(П(П(П(П(ПППП$ППП 3П3П3ППППП %П%П%П%П"П"П"П"П"П"П"rrcN) r(з__all__rrrrrrrcr*rrЗr┤sWПьпП─П""П""П""П""П""Я""Т""П""ПJ"П"П"П"П"░MЯ"Т"П"П4I"ПI"ПI"ПI"ПI"░]ЯI"ТI"ПI"ПXПППП░ ≤~ЯТПП0"П"П"П"П"≤ Я"Т"П"П23"П3"П3"П3"П3"≤-Я3"Т3"П3"ПlT"ПT"ПT"ПT"ПT"≤ ЯT"ТT"ПT"ПT"ПT"r