o lh&@s|ddlmZddlZddlZddlZddlZddlmZm Z ddgZ da ej dddkrYdd lm Zdd lmZmZdd lmZmZe d g7Z ejd krSe ddg7Z d'ddZ n.ejd kriddlZeZdZn ddlmZejZdZeZddZddZddZd'ddZ d(ddZdd Zd!d"ZGd#d$d$eZGd%d&d&eZ ej dkr eZ!e!ej"j#d<e ej"j#d<dSdS)))divisionN) LokyProcessLokyInitMainProcesslokyloky_init_main) get_context)assert_spawningset_spawning_popen)get_spawning_popen BaseContextspawnwin32fork forkservercCsN|ptpd}|dkrtdtzt|}W|Sty&td|tw)Nrrzu`fork` start method should not be used with `loky` as it does not respect POSIX. Try using `spawn` or `loky` instead.,Unknown context '{}'. Value should be in {}.)_DEFAULT_START_METHODwarningswarn UserWarningmp_get_context ValueErrorformat START_METHODS)methodcontextr W/var/www/html/env/lib/python3.10/site-packages/joblib/externals/loky/backend/context.pyr #s   r spawning_popen)Popenprocess_handlecCs tttdSN)getattr_tls popen_attrr r r r!rAs rcCsttt|dSr%)setattrr'r()popenr r r!rDsrcCs tdurtdt|jdS)NzF%s objects should only be shared between processes through inheritance)r RuntimeErrortype__name__)objr r r!r Gs r cCs8|ptpd}|dkr tS|dkrtStd|t)Nrrr)r LokyContextLokyInitMainContextrrr)rr r r!r Ns FcCs<tdur |s td|dus|tvsJd|t|adS)Nzcontext has already been setz4'{}' is not a valid start_method. It should be in {})rr+rr)rforcer r r!set_start_methodYs r2cCstSr%)rr r r r!get_start_methoddr3c Cs<ddl}zt}Wn tyd}Ynw|}ttdr0z ttd}Wn ty/Ynw|}d}d}tj |rtj |rt |d}t | }Wdn1sXwYt |d}t | }Wdn1sswY|dkr|dkrt | ||}t tjd|} t|||| } t| dS) auReturn the number of CPUs the current process can use. The returned number of CPUs accounts for: * the number of CPUs in the system, as given by ``multiprocessing.cpu_count``; * the CPU affinity settings of the current process (available with Python 3.4+ on some Unix systems); * CFS scheduler CPU bandwidth limit (available on Linux only, typically set by docker and similar container orchestration systems); * the value of the LOKY_MAX_CPU_COUNT environment variable if defined. and is given as the minimum of these constraints. It is also always larger or equal to 1. rNrsched_getaffinityz#/sys/fs/cgroup/cpu/cpu.cfs_quota_usz$/sys/fs/cgroup/cpu/cpu.cfs_period_usrLOKY_MAX_CPU_COUNT)mathmp cpu_countNotImplementedErrorhasattroslenr5pathexistsopenintreadceilenvirongetminmax) r8 cpu_count_mpcpu_count_affinity cpu_count_cfscfs_quota_fnamecfs_period_fnamefh cfs_quota_us cfs_period_uscpu_count_lokyaggregate_cpu_countr r r!r:hs<       r:c@seZdZdZdZeZeeZd#ddZ d$ddZ e j dd d krd d d Z d dZd%ddZe jdkr: ddZn* ddlmZeejZeejZeejZeejZeejZeejZeejZe jdkr d&ddZddZddZddZd$dd Zd!d"ZdSdS)'r/z#Context relying on the LokyProcess.rrNcCsddlm}||||dS)Returns a queue objectr)Queuereducersctx)queuesrTr )selfmaxsizerVrTr r r!rTs zLokyContext.QueuecCsddlm}|||dS)rSr) SimpleQueuerU)rXr[r )rYrVr[r r r!r[s zLokyContext.SimpleQueuerr cCs|Sr%r rYr r r!r r4zLokyContext.get_contextcCs|jSr%)_namer\r r r!r3szLokyContext.get_start_methodTcCs t|S)z1Returns two connection object connected by a pipe)r9Pipe)rYduplexr r r!r^s zLokyContext.PipercCsddlm}|}||S)zReturns a manager objectr) LokyManager)managersr`start)rYr`mr r r!Managers zLokyContext.Manager) synchronizercCsddlm}||dS)zReturns a semaphore objectr) Semaphore)value)rerf)rYrgrfr r r!rfs  zLokyContext.SemaphorecCddlm}||S)z"Returns a bounded semaphore objectr)BoundedSemaphore)reri)rYrgrir r r!ri zLokyContext.BoundedSemaphorecCddlm}|S)zReturns a lock objectr)Lock)rerl)rYrlr r r!rl zLokyContext.LockcCrk)zReturns a recurrent lock objectr)RLock)rern)rYrnr r r!rnrmzLokyContext.RLockcCrh)zReturns a condition objectr) Condition)rero)rYlockror r r!rorjzLokyContext.ConditioncCrk)zReturns an event objectr)Event)rerq)rYrqr r r!rqrmzLokyContext.Event)rNr%)T)r)r- __module__ __qualname____doc__r]rProcess staticmethodr:rTr[sys version_infor r3r^platformrdmultiprocessingrerfrirlrnrorqr9r r r r!r/sB                 r/c@seZdZdZdZeZdS)r0aExtra context with LokyProcess, which does load the main module This context is used for compatibility in the case ``cloudpickle`` is not present on the running system. This permits to load functions defined in the ``main`` module, using proper safeguards. The declaration of the ``executor`` should be protected by ``if __name__ == "__main__":`` and the functions and variable used from main should be out of this block. This mimics the default behavior of multiprocessing under Windows and the behavior of the ``spawn`` start method on a posix system for python3.4+. For more details, see the end of the following section of python doc https://docs.python.org/3/library/multiprocessing.html#multiprocessing-programming rN)r-rrrsrtr]rrur r r r!r0s r0r%)F)$ __future__rr=rwrrzr9processrrrrrxr rmultiprocessing.contextr rrrry threadinglocalr'r(multiprocessing.forkingr#objectr2r3r:r/r0ctx_lokyr_concrete_contextsr r r r!sN           4W