o a@sddlZddlZddlmZddlmZddlmZmZddl m Z ddl m Z m Z mZddlmZmZddlmZd d lmZmZmZmZmZGd d d ZdddZGdddZGdddZGdddeZdS)N)count)Optional) AuthenticatorBEGIN)get_bus)Message MessageTypeParser) ProxyBase unwrap_msg) message_bus)MessageFilters FilterHandle ReplyMatcher RouterClosedcheck_replyablec@s`eZdZdZdejdejfddZdddefd d Z d efd d Z ddZ ddZ ddZ dS)DBusConnectionaPA plain D-Bus connection with no matching of replies. This doesn't run any separate tasks: sending and receiving are done in the task that calls those methods. It's suitable for implementing servers: several worker tasks can receive requests and send replies. For a typical client pattern, see :class:`DBusRouter`. readerwritercCs4||_||_t|_tdd|_d|_t|_ dS)Nr )start) rrr parserroutgoing_serial unique_nameasyncioZLock send_lock)selfrrr4/usr/lib/python3/dist-packages/jeepney/io/asyncio.py__init__s  zDBusConnection.__init__Nserialmessagec sv|j4IdH&|durt|j}|j|||jIdHWdIdHdS1IdHs4wYdS)z.Serialise and send a :class:`~.Message` objectN)rnextrrwriteZ serialisedrainrr"r!rrrsend s .zDBusConnection.sendreturncsB |j}|dur |S|jdIdH}|st|j|q)z5Return the next available message from the connectionTNi)rZget_next_messagerreadEOFErrorZadd_data)rmsgbrrrreceive(s  zDBusConnection.receivecs |j|jIdHdS)zClose the D-Bus connectionN)rcloseZ wait_closedrrrrr.4s zDBusConnection.closec|SNrr/rrr __aenter__9zDBusConnection.__aenter__cs|IdHdSr1)r.rexc_typeZexc_valexc_tbrrr __aexit__<szDBusConnection.__aexit__)__name__ __module__ __qualname____doc__r StreamReader StreamWriterrrr'r-r.r2r7rrrrrs  rSESSIONc st|}t|IdH\}}t}|D]!}|||IdH|dIdH}|s0td||q|t |IdHt ||}t |4IdH}t t t|dIdH} | d|_WdIdH|S1IdHstwY|S)zHOpen a plain D-Bus connection :return: :class:`DBusConnection` Niz#Socket closed before authentication r)rrZopen_unix_connectionrr$r%r)r*Zfeedrr DBusRouterZwait_forProxyr ZHellor) busZbus_addrrrZauthrZreq_datar,connrouterZ reply_bodyrrropen_dbus_connection@s*     rEc@seZdZdZdZdZdZdefddZe ddZ ddd d Z d e fd d Z ddddeejfddZddZddZde fddZddZdS)r@zA 'client' D-Bus connection which can wait for a specific reply. This runs a background receiver task, and makes it possible to send a request and wait for the relevant reply. NrCcCs*||_t|_t|_t||_dSr1) _connr_repliesr_filtersrZ create_task _receiver _rcv_task)rrCrrrrjszDBusRouter.__init__cCs|jjSr1)rFrr/rrrrpszDBusRouter.unique_namer cs|jj||dIdHdS)z&Send a message, don't wait for a replyr N)rFr'r&rrrr'tszDBusRouter.sendr(cs|t||jrtdt|jj}|j|t }|j ||dIdH|IdHWdS1s7wYdS)zSend a method call message and wait for the reply Returns the reply message (method return or error message type). zThis DBusRouter has stoppedr N) rrJdonerr#rFrrGZcatchrZFuturer')rr"r!Z reply_futrrrsend_and_get_replyxs  $zDBusRouter.send_and_get_replyr )queuebufsizerMcCst|j||p t|S)arCreate a filter for incoming messages Usage:: with router.filter(rule) as queue: matching_msg = await queue.get() :param MatchRule rule: Catch messages matching this rule :param asyncio.Queue queue: Send matching messages here :param int bufsize: If no queue is passed in, create one with this size )rrHrQueue)rZrulerMrNrrrfilters zDBusRouter.filtercr0r1rr/rrrr2r3zDBusRouter.__aenter__csb|jr |jdS|jttj|jIdHWddS1s*wYdS)NF)rJrKresultZcancel contextlibsuppressrZCancelledErrorr4rrrr7s    zDBusRouter.__aexit__r+c CsN|j|rdSt|j|D]}z|j|Wqtjy$YqwdS)zHandle one received messageN) rGdispatchlistrHmatchesrMZ put_nowaitrZ QueueFull)rr+rPrrr _dispatchs zDBusRouter._dispatchcs.z |jIdH}||q|jw)z'Receiver loop - runs in a separate taskTN)rFr-rWrGZdrop_all)rr+rrrrIs  zDBusRouter._receiver)r8r9r:r;Z _nursery_mgrZ_send_cancel_scopeZ_rcv_cancel_scoperrpropertyrr'rrLrrrOrPr2r7rWrIrrrrr@`s  r@c@s2eZdZdZdZdZd ddZddZdd ZdS) open_dbus_routerzOpen a D-Bus 'router' to send and receive messages Use as an async context manager:: async with open_dbus_router() as router: ... Nr>cCs ||_dSr1)rB)rrBrrrrs zopen_dbus_router.__init__cs0t|jIdH|_t|j|_|jIdHSr1)rErBrCr@req_ctxr2r/rrrr2s zopen_dbus_router.__aenter__cs,|j|||IdH|jIdHdSr1)rZr7rCr.r4rrrr7szopen_dbus_router.__aexit__r>) r8r9r:r;rCrZrr2r7rrrrrYs  rYcs0eZdZdZfddZddZddZZS)rAaAn asyncio proxy for calling D-Bus methods You can call methods on the proxy object, such as ``await bus_proxy.Hello()`` to make a method call over D-Bus and wait for a reply. It will either return a tuple of returned data, or raise :exc:`.DBusErrorResponse`. The methods available are defined by the message generator you wrap. :param msggen: A message generator object. :param ~asyncio.DBusRouter router: Router to send and receive messages. cst|||_dSr1)superr_router)rZmsggenrD __class__rrrs  zProxy.__init__cCsd|j|jS)Nz Proxy({}, {}))formatZ_msggenr]r/rrr__repr__szProxy.__repr__csfdd}|S)Ncs<|i|}|jjtjusJj|IdH}t|Sr1)headerZ message_typerZ method_callr]rLr )argskwargsr+Zreplymake_msgrrrinners z!Proxy._method_call..innerr)rrfrgrrer _method_callszProxy._method_call)r8r9r:r;rrarh __classcell__rrr^rrAs  rAr[)rrR itertoolsrtypingrZ jeepney.authrrZ jeepney.busrZjeepneyrrr Zjeepney.wrappersr r Zjeepney.bus_messagesr commonrrrrrrrEr@rYrArrrrs     0 X