^ jkdZddlmZddlZddlmZddlmZmZddl m Z e rddl m Z m Z Gdd eZ Gd d ZdS) a Experimental multithreaded Job system. This module provides the `JobExecutor` class, which allows submitting batches of highly parallizable work in the form of functions and arguments. This is commonly known as "task-based multithreading" or a "multithreaded job system". ..note:: This module is only really useful with the recent Python 3.13 releases that are built with experimental free-threading support. With typical Python releases that contain a GIL, this is not of much practical use. ) annotationsN)Queue)EventThread) TYPE_CHECKING)CallableAnyc4eZdZdZdfd Zdd Zdd ZxZS)_Workerz$A worker thread to pop and run jobs. workqueuer exiteventrindexintreturnNonectd||_||_||_|dS)NT)daemon)super__init___queue_exit_indexstart)selfr r r __class__s S/home/agentuser/manim-venv/lib/python3.11/site-packages/pyglet/experimental/jobs.pyrz_Worker.__init__sD %%%    c|j}|j}|sF|\}}||||DdSdS)zParallel thread of execution.N)rris_setget task_done)rrrfuncargss rrunz _Worker.run#st ,,.. JD$ D$KK      ,,..     rstrc&|jd|jdS)Nz(id=))name native_idrs r__repr__z_Worker.__repr__,s)222222r)r rr rrrrrrrrr%)__name__ __module__ __qualname____doc__rr$r+ __classcell__)rs@rr r sk..33333333rr c<eZdZdZdddZdd Zdd ZddZddZdS) JobExecutoraGA light-weight multithreaded job system. A JobExecutor loosely mimics the design of the Executor classes from the `concurrent.futures` module, but does not share any code with those classes. Instead, it is a more light-weight implementation intended for execution of highly parallizable functions (jobs). A key difference is that JobExecutor does not return `Futures`. Submitted jobs must be self-contained, or handle returning values by other mechanisms. The :py:meth:`~sync` method can be used to wait for all currently submitted jobs to complete. N max_workers int | Nonerrc|ptjdz_t_t _fdtjD_dS)zCreate an instance of a JobExecutor. Args: max_workers: The number of threads to use. If `None`, will create half as many threads as reported CPU cores. cFg|]}tjj|S)r r _exitevent).0irs r z(JobExecutor.__init__..Fs)dddadoqAAdddrN) os cpu_count _max_workersrr;rrrange_threads)rr5s` rrzJobExecutor.__init__<s^(>2<>>Q+>''gg dddd5QUQbKcKcddd rr"rr#r cz |j||fdS#t$rtdwxYw)aSubmit a job to be executed on . A "job" consists of a function to be called, alone with any arguments that should be passed to it. Jobs are automatically executed by the next free worker thread. No values are returned when jobs are submitted, and the functions should also not return any values; return values are lost. Args: func: A function to execute. *args: Any arguments to pass to the function. z&cannot submit new tasks after shutdownN)rputAttributeError RuntimeError)rr"r#s rsubmitzJobExecutor.submitHsT I KOOT4L ) ) ) ) ) I I IGHH H Is :c|jsdS|jt|jD]}|d|jd|_d|_dS)a9Shut down the JobExecutor, terminating all worker threads. All JobExecutor workers are Daemon Threads, so it is not strictly necessary to call shutdown() at program termination. However, if it is no longer needed, shutdown() can be called to free up the thread resources. NcdSNr:r:rrz&JobExecutor.shutdown..fsr)rr;setrBrArHrCclear)r_s rshutdownzJobExecutor.shutdownZs~{  F t()) & &A KK % % % %  rc8|jdS)aWait for all currently submitted jobs to complete. This method will wait until the internal queue is empty, AND all currently submitted jobs have completed execution. It can be used to fence between separate batches of jobs that should not be run at the same time. For example:: for chunk in worklist: executor.submit(some_function, chunk) executor.sync() window.draw() N)rjoinr*s rsynczJobExecutor.syncks rr%c0|jjd|jdS)Nz (workers=r')rr.rCr*s rr+zJobExecutor.__repr__}s .)DDDMDDDDrrK)r5r6rr)r"rr#r rrr,r-) r.r/r0r1rrHrPrSr+r:rrr4r40s   e e e e eIIII$"$EEEEEErr4)r1 __future__rr?queuer threadingrrtypingrrr r r4r:rrrYs  #""""" ######## %$$$$$$$$33333f333,NENENENENENENENENENEr