uj lSSKJr SSKrSSKrSSKJr SSKJr SSKJ r J r J r SS/r S S S jjr S S jrg)) annotationsN)AbstractContextManager)TextIO) DummyInputInput PipeInput create_inputcreate_pipe_inputc[RS:XaCSSKJn Ucc [ 5$U"U=(d [R5$SSKJn Ucf[RnU(aO[R[R[R4HnUR5(dMUn O UR5 U"U5$![Ra [ 5s$f=f)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) Win32Input) Vt100Input)sysplatformr rstdinrvt100rstdoutstderrisattyfilenoioUnsupportedOperation)ralways_prefer_ttyrrobjs ګC:\Users\johnn\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.13_qbz5n2kfra8p0\LocalCache\local-packages\Python313\site-packages\prompt_toolkit/input/defaults.pyr r s ||w% =SYY.< %,399--% =IIE IIszz3::>Czz|| #? LLN%  && <  sC DDc[RS:XaSSKJn UR 5$SSKJn UR 5$)a! 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. r r)Win32PipeInput)PosixPipeInput)rr win32_pipercreate posix_piper)rrs rr r <s4 ||w.$$&&.$$&&)NF)rz TextIO | Nonerboolreturnr)r%z!AbstractContextManager[PipeInput]) __future__rrr contextlibrtypingrbaserrr __all__r r r#rr,s4" -..  )!X'r#