j `ddlmZddlZddlZddlmZmZddlmZm Z m Z ddgZ dddZ ddZ dS)) annotationsN)ContextManagerTextIO) DummyInputInput PipeInput create_inputcreate_pipe_inputFstdin TextIO | Nonealways_prefer_ttyboolreturnrctjdkr9ddlm}|tjt S||p tjSddlm}|Ltj}|r>tjtjtj fD]}| r|}n | n##tj $rt cYSwxYw||S)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 rrrobjs j/var/www/finuniver-perm.ru/html/student/venv/lib/python3.11/site-packages/prompt_toolkit/input/defaults.pyr r s  |w%%%%%% =SY.<< z%,39---%%%%%% =IE  Isz3:>Czz|| # LLNNNN&   <<    z%   sB44CCContextManager[PipeInput]ctjdkrddlm}|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#s rr r ;sY |w......$$&&&......$$&&&)NF)r r rrrr)rr ) __future__rrrtypingrrbaserrr __all__r r r'rr-s"""""" ))))))))..........  )!)!)!)!)!X''''''r'