:vj|dZddlmZddlmZmZddlZddlmZ ddl m Z  d dZ Gd d e e ZeZ d d gZy) z0MQ Frame pure Python methods.) annotations)LiteraloverloadN)Frame)AttributeSetterctjj||tjst d|y)Nz6libzmq and pyzmq must be built with draft support for )zmqerror_check_version DRAFT_API RuntimeError)vfeatures `/workspace/moltex-experiments/.pixi/envs/default/lib/python3.12/site-packages/zmq/sugar/frame.py_draftrs;IIQ( ==DWI N   ceZdZdZed dZed dZeddZddZddZeddZejddZedd Z e jdd Z y )rau A zmq message Frame class for non-copying send/recvs and access to message properties. A ``zmq.Frame`` wraps an underlying ``zmq_msg_t``. Message *properties* can be accessed by treating a Frame like a dictionary (``frame["User-Id"]``). .. versionadded:: 14.4, libzmq 4 Frames created by ``recv(copy=False)`` can be used to access message properties and attributes, such as the CURVE User-Id. For example:: frames = socket.recv_multipart(copy=False) user_id = frames[0]["User-Id"] This class is used if you want to do non-copying send and recvs. When you pass a chunk of bytes to this class, e.g. ``Frame(buf)``, the ref-count of `buf` is increased by two: once because the Frame saves `buf` as an instance attribute and another because a ZMQ message is created that points to the buffer of `buf`. This second ref-count increase makes sure that `buf` lives until all messages that use it have been sent. Once 0MQ sends all the messages and it doesn't need the buffer of ``buf``, 0MQ will call ``Py_DECREF(s)``. Parameters ---------- data : object, optional any object that provides the buffer interface will be used to construct the 0MQ message data. track : bool whether a MessageTracker_ should be created to track this object. Tracking a message has a cost at creation, because it creates a threadsafe Event object. copy : bool default: use copy_threshold Whether to create a copy of the data to pass to libzmq or share the memory with libzmq. If unspecified, copy_threshold is used. copy_threshold: int default: :const:`zmq.COPY_THRESHOLD` If copy is unspecified, messages smaller than this many bytes will be copied and messages larger than this will be shared with libzmq. cyNselfkeys r __getitem__zFrame.__getitem__KsDGrcyrrrs rrzFrame.__getitem__MsADrcyrrrs rrzFrame.__getitem__Os25rc$|j|Sr)getrs rrzFrame.__getitem__Qsxx}rcft|}d}|dkDrUtt|jdd}|dk\rd}|dz}n|dk\rd}|d z}n|d k\rd }|d z}nd }|}d |d|}n |j}|jj }|dk(rd}d|d|jj d||dS)z#Return the str form of the message.N geAGBiMBg.Ag@@kBBz...z.0fzzmq.sugar.framer <.(z)>)lenbytes memoryviewbuffer __class__ __module____name__)rnbytes msg_suffix msg_bytesunitn_modules r__repr__zFrame.__repr__UsT B;j5cr:;I}cM5cM3cMqgdV,J I..++ ' 'G7)1T^^445QymJ= 4.2 and pyzmq built with draft APIs enabled. .. versionadded:: 17  RADIO-DISHgrouprrrs rr>z Frame.groupps v|$xx  rc@tdd|jd|y)Nr:r=r>rset)rr>s rr>z Frame.group{sv|$ % rc<tdd|jdS)zThe CLIENT-SERVER routing id of the message. Requires libzmq >= 4.2 and pyzmq built with draft APIs enabled. .. versionadded:: 17 r: CLIENT-SERVER routing_idr?r@s rrFzFrame.routing_ids v'xx %%rc@tdd|jd|y)Nr:rErFrB)rrFs rrFzFrame.routing_idsv' z*rN)rzint | Literal['routing_id']returnint)rzbytes | Literal['group']rHstr)rrJrH int | str)rzint | str | bytesrHrK)rHrJ)r>z str | bytesrHNone)rHrI)rFrIrHrL) r1r0 __qualname____doc__rrr8propertyr>setterrFrrrrrs-^GG DD 55S6!! \\!!&&++rrMessage)rz3tuple[int] | tuple[int, int] | tuple[int, int, int]rrJrHrL)rN __future__rtypingrrr zmq.backendr FrameBase attrsettrrrrQ__all__rrrrXsZ$ #$ *& :    s+Is+n  I r