o žD®fÄ ã@sbddlmZddlZddlZddlmZmZddlmZm Z m Z ddgZ dddd„Z ddd„Z dS)é)Ú annotationsN)ÚContextManagerÚTextIOé)Ú DummyInputÚInputÚ PipeInputÚ create_inputÚcreate_pipe_inputFÚstdinú TextIO | NoneÚalways_prefer_ttyÚboolÚreturnrcCs®tjdkrddlm}|durtjdurtƒS||ptjƒSddlm}|dur@tj}|r@tjtjtj fD] }|  ¡r?|}nq5z |  ¡W||ƒSt j yVtƒYSw)a§ Create the appropriate `Input` object for the current os/environment. :param always_prefer_tty: When set, if `sys.stdin` is connected to a Unix `pipe`, check whether `sys.stdout` or `sys.stderr` are connected to a pseudo terminal. If so, open the tty for reading instead of reading for `sys.stdin`. (We can open `stdout` or `stderr` for reading, this is how a `$PAGER` works.) Úwin32r)Ú Win32InputN)Ú Vt100Input)ÚsysÚplatformrrr rÚvt100rÚstdoutÚstderrÚisattyÚfilenoÚioÚUnsupportedOperation)r r rrÚobj©rúV/home/ubuntu/webapp/venv/lib/python3.10/site-packages/prompt_toolkit/input/defaults.pyr s(  þ ý ÿúContextManager[PipeInput]cCs2tjdkrddlm}| ¡Sddlm}| ¡S)aA Create an input pipe. This is mostly useful for unit testing. Usage:: with create_pipe_input() as input: input.send_text('inputdata') Breaking change: In prompt_toolkit 3.0.28 and earlier, this was returning the `PipeInput` directly, rather than through a context manager. rr)ÚWin32PipeInput)ÚPosixPipeInput)rrÚ win32_piper ÚcreateÚ posix_piper!)r r!rrrr ;s  )NF)r r r rrr)rr)Ú __future__rrrÚtypingrrÚbaserrrÚ__all__r r rrrrÚs þ ,