+ LV-j.b^RIt^RIHt^RIHt^RIHtHtHt^RI H t H t ^RI H t Ht^RIHtHtHt.ROt]P(!] P*!R44t]P(!] P*!R44t!RR]4t]!RRR7!RR ]44t]!RRR7!RR]44t]!RRR7!RR ]44t]!RRR7!RR ]44t]!RRR7!RR ]44t]!RRR7!RR ]44t]!RR7!RR]44tR#)N)ABC) dataclass)ListTupleUnion)methodrequest_target)Headersnormalize_and_validate)bytesifyLocalProtocolErrorvalidateEventRequestInformationalResponseResponseData EndOfMessageConnectionClosedasciic]tRt^ tRtRtRtR#)rz Base class for h11 events. N)__name__ __module__ __qualname____firstlineno____doc__ __slots____static_attributes__r\/Volumes/fast/ai/experiments/ui-tars-smoke/.venv/lib/python3.14/site-packages/h11/_events.pyrr sIr FT)initfrozencbaa]tRt^(toRtR tRRRR/V3RlV3RllltRtV3R ltR t Vt V;t #) raThe beginning of an HTTP request. Fields: .. attribute:: method An HTTP method, e.g. ``b"GET"`` or ``b"POST"``. Always a byte string. :term:`Bytes-like objects ` and native strings containing only ascii characters will be automatically converted to byte strings. .. attribute:: target The target of an HTTP request, e.g. ``b"/index.html"``, or one of the more exotic formats described in `RFC 7320, section 5.3 `_. Always a byte string. :term:`Bytes-like objects ` and native strings containing only ascii characters will be automatically converted to byte strings. .. attribute:: headers Request headers, represented as a list of (name, value) pairs. See :ref:`the header normalization rules ` for details. .. attribute:: http_version The HTTP protocol version, represented as a byte string like ``b"1.1"``. See :ref:`the HTTP version normalization rules ` for details. http_version1.1_parsedFc <V^8dQhRS[S[S[3,RS[S[S[S[S[S[3,,S[S[S[S[3,,3,RS[S[S[3,RS[S[S[3,RS[RR/#)rheaderstargetr%r'returnN)rbytesstrr rrbool)format __classdict__s"r! __annotate__Request.__annotate__Rs(N(NeSj!(NwU5%<%8 94c3h;PPQ (N eSj! (N E3J' (N(N (Nr c F<\S V`4\V\4'd\P VRV4M!\P VR\ W%R74V'gb\P VR\V44\P VR\V44\P VR\V44ME\P VRV4\P VRV4\P VRV4^pVPFwrxVR8XgKV^, pK VPR8XdV^8Xd \R4hV^8d \R4h\\VPR 4\\VPR 4R #) r*r'rr+r%shostr&zMissing mandatory Host: headerzFound multiple Host: headerszIllegal method characterszIllegal target charactersN)super__init__ isinstancer object __setattr__r r r*r%r r method_rerrequest_target_rer+) selfrr*r+r%r' host_countnamevalue __class__s &$$$$$ r!r7Request.__init__RsI  gw ' '   tY 8   i!7!Q    tXx/? @   tXx/? @   t^Xl5K L   tXv 6   tXv 6   t^\ B <$%CD DDKK)DE"DKK1LMr NcJ<V^8dQh/S[;R&S[;R&S[;R&S[;R&#)r)rr*r+r%)r-r )r0r1s"r!r2r3(s?J MKLMN MOPQr r)rr*r+r% rrrrrrr7__hash____annotate_func__r__classdictcell__ __classcell__rAr1s@@r!rr(sEB@I(N +1 (N(N(NVHkr ctaa]tRt^toRtRRRRRR/V3RlV3RllltV3R lR ltR tV3R ltR t Vt V;t #) _ResponseBaser%reasonr&r r'Fc <V^8dQhRS[S[S[S[S[S[3,,S[S[S[S[3,,3,RS[RS[S[S[3,RS[S[S[3,RS[RR/#)r)r* status_coder%rLr'r,N)rr rrr-r.intr/)r0r1s"r!r2_ResponseBase.__annotate__swU5%<%8 94c3h;PPQ  E3J'  eSj!  r c <\SV`4\V\4'd\P VRV4M!\P VR\ WR74V'g\P VR\V44\P VR\V44\V\4'g \R4h\P VR\V44ME\P VRV4\P VRV4\P VRV4VP4R#)r*r5rLr%zstatus code must be integerrNN) r6r7r8r r9r:r r rOr __post_init__)r=r*rNr%rLr'rAs&$$$$$r!r7_ResponseBase.__init__s  gw ' '   tY 8   i!7!Q    tXx/? @   t^Xl5K Lk3//()FGG   t]C 4D E   tXv 6   t^\ B   t]K @ r c<V^8dQhRR/#r)r,Nr)r0r1s"r!r2rPs  t r cR#)Nrr=s&r!rR_ResponseBase.__post_init__s r NcJ<V^8dQh/S[;R&S[;R&S[;R&S[;R&#)r)r*r%rLrN)r r-rO)r0r1s"r!r2rPs8    M r r)r*r%rLrN) rrrrrr7rRrErFrrGrHrIs@@r!rKrKsKDI +1  %( >  HYr rKc:a]tRt^toRtV3RlRltRtRtVtR#)raAn HTTP informational response. Fields: .. attribute:: status_code The status code of this response, as an integer. For an :class:`InformationalResponse`, this is always in the range [100, 200). .. attribute:: headers Request headers, represented as a list of (name, value) pairs. See :ref:`the header normalization rules ` for details. .. attribute:: http_version The HTTP protocol version, represented as a byte string like ``b"1.1"``. See :ref:`the HTTP version normalization rules ` for details. .. attribute:: reason The reason phrase of this response, as a byte string. For example: ``b"OK"``, or ``b"Not Found"``. c<V^8dQhRR/#rUr)r0r1s"r!r2"InformationalResponse.__annotate__str c^dVPu;8:d^8g'M\RPVP44hR#)dzGInformationalResponse status_code should be in range [100, 200), not {}NrNr r0rWs&r!rR#InformationalResponse.__post_init__s<t''-#-$%%+VD,<,<%= .r Nr rrrrrrRrErrGr1s@r!rrs:Hr c:a]tRt^toRtV3RlRltRtRtVtR#)raThe beginning of an HTTP response. Fields: .. attribute:: status_code The status code of this response, as an integer. For an :class:`Response`, this is always in the range [200, 1000). .. attribute:: headers Request headers, represented as a list of (name, value) pairs. See :ref:`the header normalization rules ` for details. .. attribute:: http_version The HTTP protocol version, represented as a byte string like ``b"1.1"``. See :ref:`the HTTP version normalization rules ` for details. .. attribute:: reason The reason phrase of this response, as a byte string. For example: ``b"OK"``, or ``b"Not Found"``. c<V^8dQhRR/#rUr)r0r1s"r!r2Response.__annotate__str c^VPu;8:dR8g'M\RPVP44hR#)iz;Response status_code should be in range [200, 1000), not {}Nr_rWs&r!rRResponse.__post_init__s>t''.$.$MTT$$ /r Nrrarbs@r!rrs8Hr cNa]tRtRtoRtRtR V3RlRlltRtV3RltRt Vt R#) riaPart of an HTTP message body. Fields: .. attribute:: data A :term:`bytes-like object` containing part of a message body. Or, if using the ``combine=False`` argument to :meth:`Connection.send`, then any object that your socket writing code knows what to do with, and for which calling :func:`len` returns the number of bytes that will be written -- see :ref:`sendfile` for details. .. attribute:: chunk_start A marker that indicates whether this data object is from the start of a chunked transfer encoding chunk. This field is ignored when when a Data event is provided to :meth:`Connection.send`: it is only valid on events emitted from :meth:`Connection.next_event`. You probably shouldn't use this attribute at all; see :ref:`chunk-delimiters-are-bad` for details. .. attribute:: chunk_end A marker that indicates whether this data object is the last for a given chunked transfer encoding chunk. This field is ignored when when a Data event is provided to :meth:`Connection.send`: it is only valid on events emitted from :meth:`Connection.next_event`. You probably shouldn't use this attribute at all; see :ref:`chunk-delimiters-are-bad` for details. c0<V^8dQhRS[RS[RS[RR/#)r)data chunk_start chunk_endr,Nr-r/)r0r1s"r!r2Data.__annotate__+s-999(,9AE9 9r c\PVRV4\PVRV4\PVRV4R#)rkrlrmN)r9r:)r=rkrlrms&&&&r!r7 Data.__init__+s: 4.4 <4i8r Nc><V^8dQh/S[;R&S[;R&S[;R&#)r)rkrlrmrn)r0r1s"r!r2ros0H KIJKLOMr r)rkrlrm)FF) rrrrrrr7rErFrrGrbs@r!rrs+@5I 99Har cbaa]tRtRtoRtR tRRRR/V3RlV3RllltRtV3R ltR t Vt V;t #) ri;aJThe end of an HTTP message. Fields: .. attribute:: headers Default value: ``[]`` Any trailing headers attached to this message, represented as a list of (name, value) pairs. See :ref:`the header normalization rules ` for details. Must be empty unless ``Transfer-Encoding: chunked`` is in use. r*Nr'Fc<V^8dQhRS[S[S[S[S[S[3,,S[S[S[S[3,,R3,RS[RR/#)r)r*Nr'r,)rr rrr-r.r/)r0r1s"r!r2EndOfMessage.__annotate__QsW55 T%u -.U38_0Et K 5  5 5r c<\SV`4Vf \.4pM"\V\4'g \ WR7p\ P VRV4R#)Nr5r*)r6r7r r8r r9r:)r=r*r'rAs&$$r!r7EndOfMessage.__init__QsG  ?bkGGW--,WFG4G4r c&<V^8dQh/S[;R&#)r)r*)r )r0r1s"r!r2ru;s()r r)r*rDrIs@@r!rr;s> I5  5  55"HOr )r#c]tRtRtRtRtR#)riea)This event indicates that the sender has closed their outgoing connection. Note that this does not necessarily mean that they can't *receive* further data, because TCP connections are composed to two one-way channels which can be closed independently. See :ref:`closing` for details. No fields. rN)rrrrrrrr r!rres  r )rrrrrrr) reabcr dataclassesrtypingrrr_abnfrr _headersr r _utilr r r__all__compileencoder;r<rrrKrrrrrrr r!rs] !%%)599  JJv}}W- . JJ~44W=>C d#TeT$Tn d#+E+$+\ d#&M&$&R d#&}&$&R d#/5/$/n d#&5&$&R $  u    r