]jSrSSKrSSKrSSKrSSKJr SqSr"SS5r\"5r "SS5r S r S r S r S \S \4Sjrg)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[R"5$![a Of=f[b[R 5(a[R "5q[$)a:asyncio 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_loopW/home/mande/repo/quber/.venv/lib/python3.13/site-packages/IPython/core/async_helpers.pyget_asyncio_looprsV ''))    "&9&C&C&E&E%446 s  $$c \rSrSrSrSrSrg)_AsyncIORunner2c4[5RU5$)z Handler for asyncio autoawait )rrun_until_complete)selfcoros r __call___AsyncIORunner.__call__3s !44T::r cg)Nrr rs r __str___AsyncIORunner.__str__9sr r N)__name__ __module__ __qualname____firstlineno__rr__static_attributes__r r r rr2s ; r rc0\rSrSrSrSrSrSrSrSr g) _AsyncIOProxy@zVProxy-object for an asyncio Any coroutine methods will be wrapped in event_loop.run_ cXlX lgN)_obj _event_loop)robj event_loops r __init___AsyncIOProxy.__init__Fs  %r c$SUR<S3$)Nz<_AsyncIOProxy(z)>)r&rs r __repr___AsyncIOProxy.__repr__Js  R00r c^^[TRU5m[R"T5(a[ T5UU4Sj5nU$T$)Nc~>[R"T"U0UD6TR5n[R"U5$r%)rrun_coroutine_threadsafer' wrap_future)argskwargsconcurrent_futureattrrs r _wrapped+_AsyncIOProxy.__getattr__.._wrappedRs=$+$D$D$)&)4+;+;%!**+<==r )getattrr&inspectiscoroutinefunctionr)rkeyr7r6s` @r __getattr___AsyncIOProxy.__getattr__MsHtyy#&  & &t , ,4[ > > OKr c,[UR5$r%)dirr&rs r __dir___AsyncIOProxy.__dir__]s499~r )r'r&N) rrrr__doc__r*r-r=rAr r r r r"r"@s &1 r r"c,SSKnURU5$)z handler for curio autoawait rN)curiorun) coroutinerEs r _curio_runnerrHas 99Y r c2SSKnSnURX 5$)Nrc"# UIShvN $N7f)zv 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 loc_trio_runner..locms zzs  )triorF)async_fnrMrKs r _trio_runnerrOjs 88C ""r cURS5 [SRURS95e![anUR sSnA$SnAff=f)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_runnerrWwsR  $  3 : :T]] : S  yys5 A A AAcellreturnc [USS[[SS5S9n[RUR -[R:H$![ [[4a gf=f)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) compiler9astr: CO_COROUTINEco_flags SyntaxError ValueError MemoryError)rXcodes r _should_be_asyncrfs`  $gc3OQT&U ##dmm3w7K7KKK [ 1sAA A#"A#)rCr_rr: functoolsrrrr_asyncio_runnerr"rHrOrWstrboolrfr r r rksd  :!"B  # & 3 4 r