B 't\@sndZddlmZddlmZddlmZddlmZddl Z ddl Z dd gZ ed d dZ Gd d d e ZdS)a patch_stdout ============ This implements a context manager that ensures that print statements within it won't destroy the user interface. The context manager will replace `sys.stdout` by something that draws the output above the current prompt, rather than overwriting the UI. Usage:: with patch_stdout(): ... application.run() ... Multiple applications can run in the body of the context manager, one after the other. )unicode_literals)run_in_terminal)get_event_loop)contextmanagerN patch_stdout StdoutProxyFccsHt|d}tj}tj}|t_|t_z dVWd||t_|t_XdS)a Replace `sys.stdout` by an :class:`_StdoutProxy` instance. Writing to this proxy will make sure that the text appears above the prompt, and that it doesn't destroy the output from the renderer. If no application is curring, the behaviour should be identical to writing to `sys.stdout` directly. :param raw: (`bool`) When True, vt100 terminal escape sequences are not removed/escaped. )rawN)rsysstdoutstderrflush)r proxyoriginal_stdoutZoriginal_stderrr:lib/python3.7/site-packages/prompt_toolkit/patch_stdout.pyr"s  c@sBeZdZdZdddZddZdd Zd d Zd d ZddZ dS)rzp Proxy object for stdout which captures everything and prints output above the current application. FNcCsHt|tst|ptj}||_t|_||_ g|_ |j |_ |j |_ dS)N) isinstanceboolAssertionErrorr __stdout__r threadingRLock_lockZ_raw_buffererrorsencoding)selfr rrrr__init__Gs  zStdoutProxy.__init__cs2sdSfddfdd}t|dS)zx Write the given text to stdout and flush. If an application is running, use `run_in_terminal`. NcsjjdS)N)rwriter r)rtextrrwrite_and_flush_s z5StdoutProxy._write_and_flush..write_and_flushcstdddS)NF)Z in_executor)rr)r rrwrite_and_flush_in_loopcsz=StdoutProxy._write_and_flush..write_and_flush_in_loop)rZcall_from_executor)rrr!r)rrr r_write_and_flushUs  zStdoutProxy._write_and_flushcCsTd|krD|dd\}}|j|dg}|g|_d|}||n |j|dS)a Note: print()-statements cause to multiple write calls. (write('line') and write(' ')). Of course we don't want to call `run_in_terminal` for every individual call, because that's too expensive, and as long as the newline hasn't been written, the text itself is again overwritten by the rendering of the input command line. Therefor, we have a little buffer which holds the text until a newline is written to stdout.  rN)rsplitrjoinr"append)rdataZbeforeZafterZto_writerrrr_writels   zStdoutProxy._writecCs d|j}g|_||dS)Nr$)r&rr")rrrrr_flushs zStdoutProxy._flushc Cs |j||WdQRXdS)N)rr))rr(rrrrszStdoutProxy.writec Cs|j|WdQRXdS)z( Flush buffered output. N)rr*)rrrrr szStdoutProxy.flush)FN) __name__ __module__ __qualname____doc__rr"r)r*rr rrrrrBs )F)r.Z __future__rZ applicationrZ eventloopr contextlibrrr __all__robjectrrrrrs