eZ&ddlZddlZddlZddlZddlZddlZddlZddlZddl Z ddl m Z m Z ddl mZddlmZmZmZmZmZgdZGdd eZdd ZGd d eZGd deZGddeZddZddlZGddej:Zy)N)QT_LIBmkQApp)cprint) ClosedErrorLocalObjectProxy NoResultError ObjectProxyRemoteEventHandler)Process QtProcess ForkedProcessrr c*eZdZdZdZddZddZdZy) r a Bases: RemoteEventHandler This class is used to spawn and control a new python interpreter. It uses subprocess.Popen to start the new process and communicates with it using multiprocessing.Connection objects over a network socket. By default, the remote process will immediately enter an event-processing loop that carries out requests send from the parent process. Remote control works mainly through proxy objects:: proc = Process() ## starts process, returns handle rsys = proc._import('sys') ## asks remote process to import 'sys', returns ## a proxy which references the imported module rsys.stdout.write('hello ') ## This message will be printed from the remote ## process. Proxy objects can usually be used ## exactly as regular objects are. proc.close() ## Request the remote process shut down Requests made via proxy objects may be synchronous or asynchronous and may return objects either by proxy or by value (if they are picklable). See ProxyObject for more information. rNc |t}| t|}|tj}|durdnd|_t j d} tjjd| } | jd} |rtj} ntj|} tj| jj!d d }t jj#t jj%t jj'|j(d } t jj#t jj%t jj't(d }|j+d |d|d|r0t,j.dzdz}t,xj.dz c_nd}|tj0j3d}|rt4j6}t4j6}t5j8||ft4j6|||_t=|j:j>d||_ t=|j:jBd||_"n,t5j8||ft4j6|_tGjH|}t jJ}tj0dk(xr!tjLtjNk7}tQ|dz| | |s|nd|| tR|}tGjT||j:jV|j:jVjY|j+d| t[| fz | j]} |j:jb}|r!|je||jg}tijj|||dz||j|j+dtmjn|j$y#t^$r}|j`dk(rYd}~d}~wwxYw)a ============== ============================================================= **Arguments:** name Optional name for this process used when printing messages from the remote process. target Optional function to call after starting remote process. By default, this is startEventLoop(), which causes the remote process to handle requests from the parent process until it is asked to quit. If you wish to specify a different target, it must be picklable (bound methods are not). copySysPath If True, copy the contents of sys.path to the remote process. If False, then only the path required to import pyqtgraph is added. debug If True, print detailed information about communication with the child process. wrapStdout If True (default on windows) then stdout and stderr from the child process will be caught by the parent process and forwarded to its stdout/stderr. This provides a workaround for a python bug: http://bugs.python.org/issue3905 but has the side effect that child output is significantly delayed relative to the parent output. pyqtapis Formerly optional dictionary of PyQt API version numbers to set before importing pyqtgraph in the remote process. No longer has any effect. ============== ============================================================= NTF) localhostrauthkeyr.rz..z bootstrap.pyzStarting child process ( )win)stdinstdoutstderrrr)rwin32_child)nameportrppid targetStrpathqt_libdebugz4Listening for child process on port %d, authkey=%s.._parent)pidr'zConnected to child process.)8startEventLoopstrsys executabler'osurandommultiprocessing connectionListeneraddressr%inspect getmodulemodules__name__splitabspathjoindirname__file__debugMsgr _process_countplatform startswith subprocessPIPEPopenproc FileForwarderr_stdoutForwarderr_stderrForwarderpickledumpsgetpidprefix base_prefixdictrdumprcloserepracceptIOErrorerrnor*sendrecvr __init__atexitregister)selfr!targetr. copySysPathr'timeout wrapStdoutpyqtapisrlr"sysPathmodmodroot bootstrap procDebugrrr$r* xchg_pidsdataconnerr child_pids B/usr/lib/python3/dist-packages/pyqtgraph/multiprocess/processes.pyrWzProcess.__init__2sX6 >#F <t9D  J4-QU **R.  & & / /0@' / Ryy| hhG##F+Ckk#,,"4"4S"9!"<=Gggoobggll277??7CSCS3TVZ&[\GGGOOBGGLL1JN$[\  *iPQ  //1Q6I  " "a ' "I  007J  __F__F"((*i)@ `fouvDI%2$))2B2BHi$XD !$1$))2B2BHi$XD !"((*i)@ XDILL( iikLLG+M coo0M h%4   D$))//*  LPTVZ[bVcOdde xxzIIMM  IIcN I##D$YIUYU_U_` 34 "! 99>  s5Q Q: Q54Q55Q:c|jd|jj|jt j}|jjW|%t j|z |kDr t dt j d|jjW|jjt|dr||jjj|jjj|jj|jj|jd|jjzy)NzJoining child process..z,Timed out waiting for remote process to end.g?rGzChild process exited. (%d))r>rEpollrPtime ExceptionsleeprhhasattrrGfinishsetrHr; returncode)rZr]starts rkr;z Process.joins /0 99>>  # JJLIIKE)).."*&499;+>+H#$RSS 4 )).."*  4+ ,  ! ! ( ( , , .  ! ! ( ( , , .  ! ! & & (  ! ! & & ( 2TYY5I5IIJc&t|drV|jj5|jj5t j ||g|ddddddyt j ||g|y#1swY*xYw#1swYyxYw)NrG)rqrGlockrHr r>)rZmsgargss rkr>zProcess.debugMsgs 4+ ,&&++ B**//B&//cADAB B B  ' 'c 9D 9BB B Bs"BA;B;B BB)NNNTFrNN )r8 __module__ __qualname____doc__r?rWr;r>rvrkr r s 0NB#JK(:rvr c |r9ddl}tj|d|j|t |fzdt j jdt|f|}|r)tj|djzdt||||a tjtjd+#t$r-tjd t!j"dY6wxYw) Nr=[%d] connecting to server at port localhost:%d, authkey=%s.. rr'[%d] connected; starting remote proxy. r'{Gz?zExiting server loop.)r/rcoutrKrQr1r2Clientintr HANDLERprocessRequestsrnrprr>r-exit)r!r"rr#r'r/rhs rkr+r+s  E[ ryy{D$w-89:< >  % % , ,k3t9-Ew , WD  EE  SUWX!tT?G    # # % JJt      3 4 HHQK s$)C3DDc,eZdZdZddZdZddZdZy) ra ForkedProcess is a substitute for Process that uses os.fork() to generate a new process. This is much faster than starting a completely new interpreter and child processes automatically have a copy of the entire program state from before the fork. This makes it an appealing approach when parallelizing expensive computations. (see also Parallelizer) However, fork() comes with some caveats and limitations: - fork() is not available on Windows. - It is not possible to have a QApplication in both parent and child process (unless both QApplications are created _after_ the call to fork()) Attempts by the forked process to access Qt GUI elements created by the parent will most likely cause the child to crash. - Likewise, database connections are unlikely to function correctly in a forked child. - Threads are not copied by fork(); the new process will have only one thread that starts wherever fork() was called in the parent process. - Forked processes are unceremoniously terminated when join() is called; they are not given any opportunity to clean up. (This prevents them calling any cleanup code that was only intended to be used by the parent process) - Normally when fork()ing, open file handles are shared with the parent process, which is potentially dangerous. ForkedProcess is careful to close all file handles that are not explicitly needed--stdout, stderr, and a single pipe to the parent process. Nc d|_|dk(r |j}| t|}tj\}}i}|2|j D]\}} t j| } | ||<!tj} tj} | dk(rud|_ tj|jtjj|j!} tj"d| tj"| dzdd}|t_dD]v}|tj&vsdtj&|d z_tj&j+|d zdtj&j+|d zdxgt,_t-j0d |rd tj&vrXtj&d j3tjt5t7j6d zd zz dtj&vrXtj&dj3tjt5t7j6d zd zz t9j:|||dz| i|_|j D],\}} t?| | tA|||j<|<.||yyd|_ | |_!|jit8_"t9j:|||dz| t-j0|jFy)a When initializing, an optional target may be given. If no target is specified, self.eventLoop will be used. If None is given, no target will be called (and it will be up to the caller to properly shut down the forked process) preProxy may be a dict of values that will appear as ObjectProxy in the remote process (but do not need to be sent explicitly since they are available immediately before the call to fork(). Proxies will be availabe as self.proxies[name]. If randomReseed is True, the built-in random and numpy.random generators will be reseeded in the child process. FrNric*ddl}|j|yNr) tracebackprint_exception)rzrs rk excepthookz*ForkedProcess.__init__..excepthook5s ) ))40rv)PyQt4PySidePyQt5z.QtGuiz.QtCorec,tjdSr)r/_exitrrvrkz(ForkedProcess.__init__..CsBHHQKrvz numpy.randomi'randomr )r*)proxyIdtypeStrTr))$ hasJoined eventLoopr,r1Pipeitemsr registerObjectr/rKforkisParentsetpgrprPr-rfileno closerangerr7 QApplicationpoprX _exithandlersrYseedrrnr rW forkedProxiesr rQchildPidhandlersr;)rZr!r[preProxy randomReseedrh remoteConnproxyIDskvrr#r*fidrqtlibs rkrWzForkedProcess.__init__s Q;^^F <t9D*//1j   ( &1*99!<%  &yy{ggi !8!DM JJL JJL IIOO ##%C MM!S ! MM#a% & 1(CN6 ;CKK'?CCKKh/<KKOOE(ND9KKOOE)OT:  ;$&F OO/ 0!S[[0KK/44RYY[3tyy{SXGXY^G^C_5_`s{{*KK)..ryy{SUARSXAX=Y/YZ  ' 'j$x-T R!#D !)!1 l g+6tWVZ[cdh[iVj+k""4( l!"!DMDM    *,  '  ' 'dDN L OODII &rvc |jtjd'#t$rYn5t dt j t jY>xYwt jdy)Nrz$Error occurred in forked event loop:r) rrnrprprintr-rexc_inforrZs rkrzForkedProcess.eventLoop_sa 0$$& 4   0<= /  s%) A&0A&c|jry |jd|d tj|j d|jjd|_y#t$rYNwxYw#t $rY>   JJ4J H  JJt}}a (        s"A& A5& A21A25 BBcntj|jtjd|_y)zImmediately kill the forked remote process. This is generally safe because forked processes are already expected to _avoid_ any cleanup at exit.TN)r/killrsignalSIGKILLrrs rkrzForkedProcess.kill|s!  v~~.rv)NrNTr{)r8r}r~rrWrr;rrrvrkrrs6W't "rvrceZdZdZdZdZy)RemoteQtEventHandlerc6tj|g|i|yN)r rW)rZrzkwdss rkrWzRemoteQtEventHandler.__init__s##D84848rvcddlm}|j|_|jjj |j |jjdy)NrQtCorer|)QtrQTimertimerr]connectrrurZrs rkstartEventTimerz$RemoteQtEventHandler.startEventTimersB]]_  ""4#7#78 rvc tj|y#t$rKddlm}|j j j|jjYywxYw)Nr QtWidgets) r rrrrrinstancequitrstop)rZrs rkrz$RemoteQtEventHandler.processRequestssP   . .t 4  &  " " + + - 2 2 4 JJOO  sAA,+A,N)r8r}r~rWrrrrvrkrrs9 rvrc0eZdZdZdZdZddZdZdZy) ra QtProcess is essentially the same as Process, with two major differences: - The remote process starts by running startQtEventLoop() which creates a QApplication in the remote process and uses a QTimer to trigger remote event processing. This allows the remote process to have its own GUI. - A QTimer is also started on the parent process which polls for requests from the child process. This allows Qt signals emitted within the child process to invoke slots on the parent process and vice-versa. This can be disabled using processRequests=False in the constructor. Example:: proc = QtProcess() rQtGui = proc._import('PyQt4.QtGui') btn = rQtWidgets.QPushButton('button on child process') btn.show() def slot(): print('slot invoked on parent process') btn.clicked.connect(proxy(slot)) # be sure to send a proxy of the slot c d|vr t|d<ddlm}|jdd|_|jr%|j j tdtj|fi||jy)Nr[rrrTz[Must create QApplication before starting QtProcess, or use QtProcess(processRequests=False)) startQtEventLooprrr_processRequestsrrror rWr)rZrrs rkrWzQtProcess.__init__sv 4 -DN !%):D A  Y%;%;%D%D%F%Nyz z&& rvctddlm}|j|_|jr|j yy)Nrr)rrrrrstartRequestProcessingrs rkrzQtProcess.startEventTimers,]]_   ' ' ) !rvc|jjj|j|jj t |dzy)zStart listening for requests coming from the child process. This allows signals to be connected from the child process to the parent. iN)rr]rrrur)rZintervals rkrz QtProcess.startRequestProcessings= ""4#7#78 Xd]+,rvc8|jjyr)rrrs rkstopRequestProcessingzQtProcess.stopRequestProcessings rvc tj|y#t$r|jj YywxYwr)r rrrrrs rkrzQtProcess.processRequestss2   # #D )  JJOO  s #>>N)r) r8r}r~rrWrrrrrrvrkrrs 0 * -rvrc B|r9ddl}tj|d|j|t |fzdt j jdt|f|}|r)tj|djzdddl m }|jj}|t}|jd t|||| at j#t%|d r|j'y|j)y) NrrrrrrrrFrexec)r/rrrKrQr1r2rrrrrrrsetQuitOnLastWindowClosedrrrrqrexec_) r!r"rr#r'r/rhrapps rkrrs  E[_h_a_h_h_jlprvw~r_AACE F  % % , ,k3t9-Ew , WD  EE  SUWX  ) ) +C {h %%e,#4t5AG #v&CHHJCIIKrvceZdZdZdZdZy)rFa- Background thread that forwards data from one pipe to another. This is used to catch data from stdout/stderr of the child process and print it back out to stdout/stderr. We need this because this bug: http://bugs.python.org/issue3905 _requires_ us to catch stdout/stderr. *output* may be a file or 'stdout' or 'stderr'. In the latter cases, sys.stdout/stderr are retrieved once for every line that is output, which ensures that the correct behavior is achieved even if sys.stdout/stderr are replaced at runtime. ctjj|||_||_tj |_d|_||_tj|_ |jy)NT) threadingThreadrWinputoutputLockrxdaemoncolorEventrrru)rZrrrs rkrWzFileForwarder.__init__sW!!$'  NN$   oo'  rvc|jdk(r|jdur|jjs{|jj }|j 5tj|j|jddddd|jjszyy|jdk(r|jdur|jjs{|jj }|j 5tj|j|jddddd|jjszyyt|jtrtt|j|_|jjsu|jj }|j 5|jj|jdddd|jjstyy#1swYxYw#1swYxYw#1swY?xYw)NrFutf8rr)rrrris_setrreadlinerxrrdecodecerr isinstancer,getattrr-write)rZlines rkrunzFileForwarder.runs ;;( "tzz'>kk((*zz**,YYEKK DKK,?DEkk((*[[H $5)@kk((*zz**,YYEKK DKK,?DEkk((* $++s+%c4;;7 kk((*zz**,YY;KK%%dkk&&9:;kk((*EE EE;;s$1H01H= +I 0H:=I IN)r8r}r~rrWrrrvrkrFrFs ;rvrF)F)rXr5multiprocessing.connectionr1r/rrBr-rnrIrrrutilr remoteproxyrr r r r __all__r r+rrrrrrrFrrvrkrs !   T{: {:|(X&X|-&99v8((;I$$(;rv