oidZddlZddlZddlZddlmZdadZGddZeZ GddZ d Z d Z d Z d ed efdZy)a Async helper function that are invalid syntax on Python 3.5 and below. This code is best effort, and may have edge cases not behaving as expected. In particular it contain a number of heuristics to detect whether code is effectively async and need to run in an event loop or not. Some constructs (like top-level `return`, or `yield`) are taken care of explicitly to actually raise a SyntaxError and stay as close as possible to Python semantics. N)wrapsc tjS#t$rYnwxYwttj rtj atS)aZasyncio has deprecated get_event_loop Replicate it here, with our desired semantics: - always returns a valid, not-closed loop - not thread-local like asyncio's, because we only want one loop for IPython - if called from inside a coroutine (e.g. in ipykernel), return the running loop .. versionadded:: 8.0 )asyncioget_running_loop RuntimeError_asyncio_event_loop is_closednew_event_loopb/home/ubuntu/docker-apps/notebooks/venv/lib/python3.12/site-packages/IPython/core/async_helpers.pyget_asyncio_looprsS ''))    "&9&C&C&E%446 s  ""ceZdZdZdZy)_AsyncIORunnerc4tj|S)z/ Handler for asyncio autoawait )rrun_until_complete)selfcoros r __call__z_AsyncIORunner.__call__3s !44T::r cy)Nrr rs r __str__z_AsyncIORunner.__str__9sr N)__name__ __module__ __qualname__rrr r r rr2s ; r rc(eZdZdZdZdZdZdZy) _AsyncIOProxyz^Proxy-object for an asyncio Any coroutine methods will be wrapped in event_loop.run_ c ||_||_yN)_obj _event_loop)robj event_loops r __init__z_AsyncIOProxy.__init__Fs %r c"d|jdS)Nz<_AsyncIOProxy(z)>)r rs r __repr__z_AsyncIOProxy.__repr__Js  R00r ctj|tjrt fd}|SS)Ncztj|i|j}tj|Sr)rrun_coroutine_threadsafer! wrap_future)argskwargsconcurrent_futureattrrs r _wrappedz+_AsyncIOProxy.__getattr__.._wrappedRs=$+$D$D$)&)4+;+;%!**+<==r )getattrr inspectiscoroutinefunctionr)rkeyr/r.s` @r __getattr__z_AsyncIOProxy.__getattr__MsEtyy#&  & &t ,4[ > > OKr c,t|jSr)dirr rs r __dir__z_AsyncIOProxy.__dir__]s499~r N)rrr__doc__r$r&r4r7r r r rr@s &1 r rc,ddl}|j|S)z% handler for curio autoawait rN)curiorun) coroutiner:s r _curio_runnerr=as 99Y r c4ddl}d}|j||S)Nrc"K|d{S7w)z We need the dummy no-op async def to protect from trio's internal. See https://github.com/python-trio/trio/issues/89 Nr )rs r locz_trio_runner..locms zzs  )trior;)async_fnrAr@s r _trio_runnerrCjs 88C ""r c |jdtdj|j#t$r}|j cYd}~Sd}~wwxYw)z A runner that does not really allow async execution, and just advance the coroutine. See discussion in https://github.com/python-trio/trio/issues/608, Credit to Nathaniel Smith Nz%{coro_name!r} needs a real async loop) coro_name)sendrformatr StopIterationvalue)rexcs r _pseudo_sync_runnerrKwsR  $  3 : :T]] : S  yys8 A A AAcellreturnc  t|ddttdd}tj|j ztjk(S#t ttf$rYywxYw)zDetect if a block of code needs to be wrapped in an `async def` If the code block has a top-level return statement or is otherwise invalid, `False` will be returned. z<>execPyCF_ALLOW_TOP_LEVEL_AWAITr)flagsF) compiler0astr1 CO_COROUTINEco_flags SyntaxError ValueError MemoryError)rLcodes r _should_be_asyncrZs`  $gc3OQT&U ##dmm3w7K7KKK [ 1sA AA%$A%)r8rSrr1 functoolsrrrr_asyncio_runnerrr=rCrKstrboolrZr r r r_sd  :!"B  # & 3 4 r