o h @sbddlmZddlZddlZddlmZmZddlmZm Z m Z ddgZ ddddZ dddZ dS)) annotationsN)ContextManagerTextIO) DummyInputInput PipeInput create_inputcreate_pipe_inputFstdin TextIO | Nonealways_prefer_ttyboolreturnrcCstjdkrddlm}|durtjdurtS||ptjSddlm}|dur@tj}|r@tjtjtj fD] }| r?|}nq5z | W||St j yVtYSw)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)sysplatformrrr rvt100rstdoutstderrisattyfilenoioUnsupportedOperation)r r rrobjr_/var/www/html/optinet_system/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__rrrtypingrrbaserrr__all__r r rrrrs  ,