§ %Qòc¦ã óÈ—UddlZddlmZddlmZmZmZmZ ddlm Z n#e $r ddl m Z YnwxYwerddl m Z ddlmZddlmZgd ¢ZGd „d ¦«Ze d e¦«¬ ¦«Ze d ed <defd„Zdd„Zdedfd„Zedddedfd„¦«Ze ddeddeddeeddffd„¦«Zedeeddffd„¦«ZdS)éN)Úcontextmanager)Ú TYPE_CHECKINGÚAnyÚ GeneratorÚOptional)Ú ContextVar)ÚInput)ÚOutputé)Ú Application)Ú AppSessionÚget_app_sessionÚget_appÚget_app_or_noneÚset_appÚcreate_app_sessionÚcreate_app_session_from_ttycó~—eZdZdZ d deddedddfd„Zdefd „Zed d „¦«Z edd „¦«Z dS)r aZ 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` explicitely. :param output: Use this as a default output. NÚinputr Úoutputr Úreturncó0—||_||_d|_dS©N)Ú_inputÚ_outputÚapp)Úselfrrs úBlib/python3.11/site-packages/prompt_toolkit/application/current.pyÚ__init__zAppSession.__init__,s€ðˆŒ ؈Œ ð26ˆŒˆˆócó—d|j›dS)NzAppSession(app=ú))r)rs rÚ__repr__zAppSession.__repr__7s€Ø. ¤Ð.Ð.Ð.Ð.r cóH—|j€ddlm}|¦«|_|jS)Nr©Ú create_input)rÚprompt_toolkit.input.defaultsr&)rr&s rrzAppSession.input:s3€à Œ;ð )Ø BÐ BÐ BÐ BÐ BÐ Bà&˜,™.œ.ˆDŒKØŒ{Ðr cóH—|j€ddlm}|¦«|_|jS)Nr©Ú create_output)rÚprompt_toolkit.output.defaultsr*)rr*s rrzAppSession.outputBs3€à Œ<ð +Ø DÐ DÐ DÐ DÐ DÐ Dà(˜=™?œ?ˆDŒLØŒ|Ðr ©NN)rr )rr ) Ú__name__Ú __module__Ú __qualname__Ú__doc__rrÚstrr#Úpropertyrr©r rr r s»€€€€€ððð"MQð 6ð 6ؘgÔ&ð 6Ø7?ÀÔ7Ið 6à ð 6ð 6ð 6ð 6ð/˜#ð/ð/ð/ð/ððððñ„Xðððððñ„Xðððr r Ú_current_app_session)Údefaultrcó4—t ¦«Sr)r4Úgetr3r rrrPs€Ý × #Ò #Ñ %Ô %Ð%r úApplication[Any]cóp—t ¦«}|j|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)r4r7rÚdummyr:)Úsessionr:s rrrTsH€õ&#×&Ò&Ñ(Ô(€GØ„{ðØŒ{Ðà'Ð'Ð'Ð'Ð'Ð'à Ð Ñ Ô Ðr cóB—t ¦«}|jS)zj Get the current active (running) Application, or return `None` if no application is running. ©r4r7r)r<s rrrps€õ #×&Ò&Ñ(Ô(€GØ Œ;Ðr r)NNNc#óˆK—t ¦«}|j}||_ dV—||_dS#||_wxYw)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>)rr<Ú previous_apps rrrysSèè€õ#×&Ò&Ñ(Ô(€Gà”;€LØ€G„Kð#Ø ˆˆˆà"ˆŒ ˆ ˆ ølˆŒ Ð"Ð"Ð"Ð"s «8¸ Arr rr c#ónK—tjdkrtd¦«‚|€t¦«j}|€t¦«j}t ||¬¦«}t |¦«} |V—t  |¦«dS#t  |¦«wxYw)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. This functionality uses contextvars and requires at least Python 3.7. )ééz(Application sessions require Python 3.7.N©rr) ÚsysÚ version_infoÚ RuntimeErrorrrrr r4ÚsetÚreset)rrr<Útokens rrrsÀèè€õ Ô˜6Ò!ðGÝÐEÑFÔFÐFð ð(ÝÑ!Ô!Ô'ˆØ ð*Ý Ñ"Ô"Ô)ˆõ˜u¨VÐ4Ñ4Ô4€Gå × $Ò $ WÑ -Ô -€Eð*؈ ˆ ˆ å×"Ò" 5Ñ)Ô)Ð)Ð)Ð)øÕ×"Ò" 5Ñ)Ô)Ð)Ð)øøøs Á8BÂB4c#ó®K—ddlm}ddlm}|d¬¦«}|d¬¦«}t ||¬¦«5}|V—ddd¦«dS#1swxYwYdS)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_ttyrDN)r'r&r+r*r)r&r*rrÚ app_sessions rrr®sÐèè€ð ;Ð:Ð:Ð:Ð:Ð:Ø<Ð<Ð<Ð<Ð<Ð<à ˆL¨4Ð 0Ñ 0Ô 0€EØ ˆ]¨TÐ 2Ñ 2Ô 2€Få  %°Ð 7Ñ 7Ô 7ð¸;ØÐÐÐðððñôðððððððøøøððððððs¸A Á AÁA)rr8r,)rEÚ contextlibrÚtypingrrrrÚ contextvarsrÚ ImportErrorÚ*prompt_toolkit.eventloop.dummy_contextvarsÚprompt_toolkit.input.baser Úprompt_toolkit.output.baser Ú applicationr Ú__all__r r4Ú__annotations__rrrrrrr3r rúrXsdðØ € € € € Ø%Ð%Ð%Ð%Ð%Ð%Ø:Ð:Ð:Ð:Ð:Ð:Ð:Ð:Ð:Ð:Ð:Ð:ðFØ&Ð&Ð&Ð&Ð&Ð&Ð&øØðFðFðFØEÐEÐEÐEÐEÐEÐEÐEðFøøøðð)Ø/Ð/Ð/Ð/Ð/Ð/Ø1Ð1Ð1Ð1Ð1Ð1à(Ð(Ð(Ð(Ð(Ð(ð ð ð €ð-ð-ð-ð-ð-ñ-ô-ð-ð`2<°Ø J J¡L¤Lð2ñ2ô2Ðj Ô.ððñð &˜ð&ð&ð&ð&ððððð8˜Ð"4Ô5ðððððð#Ð#ð#¨ Ð2BÔ(Cð#ð#ð#ñ„ð#ð*àBFð*ð*Ø GÔ ð*Ø-5°hÔ-?ð*àˆz˜4 Ð%Ô&ð*ð*ð*ñ„ð*ð<ð Y¨z¸4ÀÐ/EÔ%Fðððñ„ðððs ™   .­.