o wh=@sUddlmZddlmZddlmZddlmZmZm Z er1ddl m Z ddl m Z ddlmZgd ZGd d d Zed ed Zded <d&ddZd'ddZd(ddZed)ddZe d*d+d"d#Zed,d$d%ZdS)-) annotations)contextmanager) ContextVar) TYPE_CHECKINGAny Generator)Input)Output) Application) AppSessionget_app_sessionget_appget_app_or_noneset_appcreate_app_sessioncreate_app_session_from_ttyc@sDeZdZdZ ddd d Zdd d ZedddZedddZdS)r aY An AppSession is an interactive session, usually connected to one terminal. Within one such session, interaction with many applications can happen, one after the other. The input/output device is not supposed to change during one session. Warning: Always use the `create_app_session` function to create an instance, so that it gets activated correctly. :param input: Use this as a default input for all applications running in this session, unless an input is passed to the `Application` explicitly. :param output: Use this as a default output. Ninput Input | Noneoutput Output | NonereturnNonecCs||_||_d|_dSN)_input_outputapp)selfrrrT/var/www/html/env/lib/python3.10/site-packages/prompt_toolkit/application/current.py__init__)s zAppSession.__init__strcCsd|jdS)NzAppSession(app=))r)rrrr__repr__3szAppSession.__repr__rcC$|jdurddlm}||_|jS)Nr create_input)rprompt_toolkit.input.defaultsr&)rr&rrrr6  zAppSession.inputr cCr$)Nr create_output)rprompt_toolkit.output.defaultsr*)rr*rrrr>r(zAppSession.outputNN)rrrrrr)rr!)rr)rr ) __name__ __module__ __qualname____doc__r r#propertyrrrrrrr s  r _current_app_session)defaultzContextVar[AppSession]rcCstSr)r2getrrrrr Lsr Application[Any]cCs*t}|jdur |jSddlm}|S)a' Get the current active (running) Application. An :class:`.Application` is active during the :meth:`.Application.run_async` call. We assume that there can only be one :class:`.Application` active at the same time. There is only one terminal window, with only one stdin and stdout. This makes the code significantly easier than passing around the :class:`.Application` everywhere. If no :class:`.Application` is running, then return by default a :class:`.DummyApplication`. For practical reasons, we prefer to not raise an exception. This way, we don't have to check all over the place whether an actual `Application` was returned. (For applications like pymux where we can have more than one `Application`, we'll use a work-around to handle that.) Nr )DummyApplication)r2r4rdummyr6)sessionr6rrrrPs   rApplication[Any] | NonecCst}|jS)zj Get the current active (running) Application, or return `None` if no application is running. r2r4r)r8rrrrlsrrGenerator[None, None, None]ccs2t}|j}||_z dVW||_dS||_w)a Context manager that sets the given :class:`.Application` active in an `AppSession`. This should only be called by the `Application` itself. The application will automatically be active while its running. If you want the application to be active in other threads/coroutines, where that's not the case, use `contextvars.copy_context()`, or use `Application.context` to run it in the appropriate context. Nr:)rr8 previous_apprrrrus rNrrrr!Generator[AppSession, None, None]c cs\|dur tj}|durtj}t||d}t|}z |VWt|dSt|w)z Create a separate AppSession. This is useful if there can be multiple individual `AppSession`s going on. Like in the case of an Telnet/SSH server. Nrr)r rrr r2setreset)rrr8tokenrrrrs  rccsfddlm}ddlm}|dd}|dd}t||d }|VWddS1s,wYdS)a Create `AppSession` that always prefers the TTY input/output. Even if `sys.stdin` and `sys.stdout` are connected to input/output pipes, this will still use the terminal for interaction (because `sys.stderr` is still connected to the terminal). Usage:: from prompt_toolkit.shortcuts import prompt with create_app_session_from_tty(): prompt('>') rr%r)T)always_prefer_ttyr>N)r'r&r+r*r)r&r*rr app_sessionrrrrs    "r)rr )rr5)rr9)rr5rr;r,)rrrrrr=)rr=) __future__r contextlibr contextvarsrtypingrrrprompt_toolkit.input.baserprompt_toolkit.output.baser applicationr __all__r r2__annotations__r rrrrrrrrrs.      /