fdZddlZddlZddlZddlmZdadZGddZeZ 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_loopU/var/www/cvtools/html/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__4s !44T::r cy)Nrr rs r __str__z_AsyncIORunner.__str__:sr N)__name__ __module__ __qualname__rrr r r rr3s ; 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__Gs %r c"d|jdS)Nz<_AsyncIOProxy(z)>)r rs r __repr__z_AsyncIOProxy.__repr__Ks  R00r ctj|tjrt fd}|SS)Ncztj|i|j}tj|Sr)rrun_coroutine_threadsafer! wrap_future)argskwargsconcurrent_futureattrrs r _wrappedz+_AsyncIOProxy.__getattr__.._wrappedSs=$+$D$D$)&)4+;+;%!**+<==r )getattrr inspectiscoroutinefunctionr)rkeyr/r.s` @r __getattr__z_AsyncIOProxy.__getattr__NsEtyy#&  & &t ,4[ > > OKr c,t|jSr)dirr rs r __dir__z_AsyncIOProxy.__dir__^s499~r N)rrr__doc__r$r&r4r7r r r rrAs &1 r rc,ddl}|j|S)z% handler for curio autoawait rN)curiorun) coroutiner:s r _curio_runnerr=bs 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..locns zzs  )trior;)async_fnrAr@s r _trio_runnerrCks 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_runnerrKxsR  $  3 : :T]] : S  yys8 A A AAcellreturnc  t|ddttdd}tj|j ztjk(S#t tf$rYywxYw)aDetect if a block of code need to be wrapped in an `async def` Attempt to parse the block of code, it it compile we're fine. Otherwise we wrap if and try to compile. If it works, assume it should be async. Otherwise Return False. Not handled yet: If the block of code has a return statement as the top level, it will be seen as async. This is a know limitation. z<>execPyCF_ALLOW_TOP_LEVEL_AWAITr)flagsF)compiler0astr1 CO_COROUTINEco_flags SyntaxError MemoryError)rLcodes r _should_be_asyncrYs^ $gc3OQT&U ##dmm3w7K7KKK  %sA AA A )r8rSrr1 functoolsrrrr_asyncio_runnerrr=rCrKstrboolrYr r r r^sd  :!"B  # &34r