a xd6@sddlZddlZddlZddlZddlmZddlZddlZddl Z ddl m Z ddl Z ddl mZddlmZmZmZmZmZddlmZeZedZd ZeZd d Zejd d d dGdddZed ddddZddddZ ddddZ!ddddZ"dS)N)count)current_async_library_cvar)CapacityLimiter)enable_ki_protectiondisable_ki_protectionRunVar TrioTokenstart_thread_sooncoroutine_or_errorlimiter(cCs6z t}Wn$ty0tt}t|Yn0|S)zGet the default `~trio.CapacityLimiter` used by `trio.to_thread.run_sync`. The most common reason to call this would be if you want to modify its :attr:`~trio.CapacityLimiter.total_tokens` attribute. )_limiter_localget LookupErrorr DEFAULT_LIMITset)r rE/var/www/html/Ranjet/env/lib/python3.9/site-packages/trio/_threads.pycurrent_default_thread_limiter$s   rTF)frozeneqhashc@seZdZeZdS)ThreadPlaceholderN)__name__ __module__ __qualname__attribnamerrrrr8sr) cancellabler c stjIdHtdur&ttjgdtt}t|fddtj fdd}t }t |j|}fdd}IdHzt||WnYn0fd d } tj| IdHS) uConvert a blocking operation into an async operation using a thread. These two lines are equivalent:: sync_fn(*args) await trio.to_thread.run_sync(sync_fn, *args) except that if ``sync_fn`` takes a long time, then the first line will block the Trio loop while it runs, while the second line allows other Trio tasks to continue working while ``sync_fn`` runs. This is accomplished by pushing the call to ``sync_fn(*args)`` off into a worker thread. From inside the worker thread, you can get back into Trio using the functions in `trio.from_thread`. Args: sync_fn: An arbitrary synchronous callable. *args: Positional arguments to pass to sync_fn. If you need keyword arguments, use :func:`functools.partial`. cancellable (bool): Whether to allow cancellation of this operation. See discussion below. limiter (None, or CapacityLimiter-like object): An object used to limit the number of simultaneous threads. Most commonly this will be a `~trio.CapacityLimiter`, but it could be anything providing compatible :meth:`~trio.CapacityLimiter.acquire_on_behalf_of` and :meth:`~trio.CapacityLimiter.release_on_behalf_of` methods. This function will call ``acquire_on_behalf_of`` before starting the thread, and ``release_on_behalf_of`` after the thread has finished. If None (the default), uses the default `~trio.CapacityLimiter`, as returned by :func:`current_default_thread_limiter`. **Cancellation handling**: Cancellation is a tricky issue here, because neither Python nor the operating systems it runs on provide any general mechanism for cancelling an arbitrary synchronous function running in a thread. This function will always check for cancellation on entry, before starting the thread. But once the thread is running, there are two ways it can handle being cancelled: * If ``cancellable=False``, the function ignores the cancellation and keeps going, just like if we had called ``sync_fn`` synchronously. This is the default behavior. * If ``cancellable=True``, then this function immediately raises `~trio.Cancelled`. In this case **the thread keeps running in background** – we just abandon it to do whatever it's going to do, and silently discard any return value or errors that it raises. Only use this if you know that the operation is safe and side-effect free. (For example: :func:`trio.socket.getaddrinfo` uses a thread with ``cancellable=True``, because it doesn't really affect anything if a stray hostname lookup keeps running in the background.) The ``limiter`` is only released after the thread has *actually* finished – which in the case of cancellation may be some time after this function has returned. If :func:`trio.run` finishes before the thread does, then the limiter release method will never be called at all. .. warning:: You should not use this function to call long-running CPU-bound functions! In addition to the usual GIL-related reasons why using threads for CPU-bound work is not very effective in Python, there is an additional problem: on CPython, `CPU-bound threads tend to "starve out" IO-bound threads `__, so using threads for CPU-bound work is likely to adversely affect the main thread running Trio. If you need to do this, you're better off using a worker process, or perhaps PyPy (which still has a GIL, but may do a better job of fairly allocating CPU time between threads). Returns: Whatever ``sync_fn(*args)`` returns. Raises: Exception: Whatever ``sync_fn(*args)`` raises. Nztrio.to_thread.run_sync-cs<fdd}t|ddur8tjddS)Nc s&zWS0dSN)unwraprelease_on_behalf_ofr)r placeholderresultrrdo_release_then_return_results  z`to_thread_run_sync..report_back_in_trio_thread_fn..do_release_then_return_resultr)outcomecapturetriolowlevelZ reschedule)r&r')r r% task_registerr&rreport_back_in_trio_thread_fns  z9to_thread_run_sync..report_back_in_trio_thread_fncsVtdt_z:}t|rB|tdt d|Wt`St`0dSNzBTrio expected a sync function, but {!r} appears to be asynchronousr) rr TOKEN_LOCALtokeninspect iscoroutineclose TypeErrorformatgetattrret)argscurrent_trio_tokensync_fnrr worker_fns   z%to_thread_run_sync..worker_fncs*z|Wntjy$Yn0dSr") run_sync_soonr*RunFinishedErrorr-)r;r.rrdeliver_worker_fn_resultsz4to_thread_run_sync..deliver_worker_fn_resultcs$rdd<tjjjStjjjSdS)Nr)r*r+ZAbortZ SUCCEEDEDZFAILED)_)r!r,rraborts z!to_thread_run_sync..abort)r*r+Zcheckpoint_if_cancelledboolr current_tasknext_thread_counterrr; contextvars copy_context functoolspartialrunZacquire_on_behalf_ofr r$Zwait_task_rescheduled) r<r!r r:r r=contextZcontextvars_aware_worker_fnr@rBr)r:r!r;r r%r.r<r,rto_thread_run_sync=s*O    rM) trio_tokencGs|rt|tstd|s@z tj}Wnty>tdYn0ztjWnty`Yn 0tdt }| |j ||||| S)zHelper function for from_thread.run and from_thread.run_sync. Since this internally uses TrioToken.run_sync_soon, all warnings about raised exceptions canceling all tasks should be noted. z0Passed kwarg trio_token is not of type TrioTokenz=this thread wasn't created by Trio, pass kwarg trio_token=...z2this is a blocking function; call it from a thread) isinstancer RuntimeErrorr0r1AttributeErrorr*r+rD stdlib_queue SimpleQueuer>rKrr#)cbfnrLrNr:qrrr_run_fn_as_system_tasks"    rWcGs8dd}t}|tjdt||g|R||dS)aRun the given async function in the parent Trio thread, blocking until it is complete. Returns: Whatever ``afn(*args)`` returns. Returns or raises whatever the given function returns or raises. It can also raise exceptions of its own: Raises: RunFinishedError: if the corresponding call to :func:`trio.run` has already completed, or if the run has started its final cleanup phase and can no longer spawn new system tasks. Cancelled: if the corresponding call to :func:`trio.run` completes while ``afn(*args)`` is running, then ``afn`` is likely to raise :exc:`trio.Cancelled`, and this will propagate out into RuntimeError: if you try calling this from inside the Trio thread, which would otherwise cause a deadlock. AttributeError: if no ``trio_token`` was provided, and we can't infer one from context. TypeError: if ``afn`` is not an asynchronous function. **Locating a Trio Token**: There are two ways to specify which `trio.run` loop to reenter: - Spawn this thread from `trio.to_thread.run_sync`. Trio will automatically capture the relevant Trio token and use it when you want to re-enter Trio. - Pass a keyword argument, ``trio_token`` specifying a specific `trio.run` loop to re-enter. This is useful in case you have a "foreign" thread, spawned using some other framework, and still want to enter Trio. c sltfddfdd}t}ztjj||dWn(tyft t dYn0dS)NcstgR}|IdHSr"r )coro)afnr:rrunprotected_afnsz:from_thread_run..callback..unprotected_afncstIdHdSr") put_nowaitr(Zacapturer)rVrZrrawait_in_trio_thread_task"szDfrom_thread_run..callback..await_in_trio_thread_task)r rLzsystem nursery is closed) rrGrHr*r+Zspawn_system_taskrPr[r(Errorr?)rVrYr:r\rLr)rYr:rVrZrcallbacks  z!from_thread_run..callbackr*rLrN)rGrHrKrrrW)rYrNr:r^rLrrrfrom_thread_runs#r`cGs*dd}t}t||g|R||dS)aRun the given sync function in the parent Trio thread, blocking until it is complete. Returns: Whatever ``fn(*args)`` returns. Returns or raises whatever the given function returns or raises. It can also raise exceptions of its own: Raises: RunFinishedError: if the corresponding call to `trio.run` has already completed. RuntimeError: if you try calling this from inside the Trio thread, which would otherwise cause a deadlock. AttributeError: if no ``trio_token`` was provided, and we can't infer one from context. TypeError: if ``fn`` is an async function. **Locating a Trio Token**: There are two ways to specify which `trio.run` loop to reenter: - Spawn this thread from `trio.to_thread.run_sync`. Trio will automatically capture the relevant Trio token and use it when you want to re-enter Trio. - Pass a keyword argument, ``trio_token`` specifying a specific `trio.run` loop to re-enter. This is useful in case you have a "foreign" thread, spawned using some other framework, and still want to enter Trio. cs4tdtfdd}t|}||dS)Nr*cs4}t|r0|tdtd|Sr/)r2r3r4r5r6r7r8r:rUrrunprotected_fn\s  z>from_thread_run_sync..callback..unprotected_fn)rrrr(r)r[)rVrUr:rbresrrarr^Ys   z&from_thread_run_sync..callbackr_)rGrHrW)rUrNr:r^rLrrrfrom_thread_run_sync:srd)#rG threadingqueuerRrI itertoolsrrr2r(Zsniffiorr*Z_syncrZ_corerrrr r Z_utilr localr0rrrFrsrrMrWr`rdrrrrs2    A