§
    ½ÞMh?  ã                  ó"  — U d dl mZ d dlmZ d dlmZ d dlmZmZm	Z	 erd dl
mZ d dlmZ ddlmZ g d	¢Z G d
„ d¦  «        Z ed e¦   «         ¬¦  «        Zded<   d d„Zd!d„Zd"d„Zed#d„¦   «         Ze	 d$d%d„¦   «         Zed&d„¦   «         ZdS )'é    )Úannotations)Úcontextmanager)Ú
ContextVar)ÚTYPE_CHECKINGÚAnyÚ	Generator)ÚInput)ÚOutputé   )ÚApplication)Ú
AppSessionÚget_app_sessionÚget_appÚget_app_or_noneÚset_appÚcreate_app_sessionÚcreate_app_session_from_ttyc                  óV   — e Zd ZdZ	 ddd	„Zdd„Zedd„¦   «         Zedd„¦   «         ZdS )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.
    NÚinputúInput | NoneÚoutputúOutput | NoneÚreturnÚNonec                ó0   — || _         || _        d | _        d S ©N)Ú_inputÚ_outputÚapp)Úselfr   r   s      úb/var/www/html/test/jupyter/venv/lib/python3.11/site-packages/prompt_toolkit/application/current.pyÚ__init__zAppSession.__init__)   s   € ð ˆŒØˆŒð -1ˆŒˆˆó    Ústrc                ó   — d| j         ›dS )NzAppSession(app=ú))r   )r    s    r!   Ú__repr__zAppSession.__repr__3   s   € Ø. ¤Ð.Ð.Ð.Ð.r#   r	   c                óH   — | j         €ddlm}  |¦   «         | _         | j         S )Nr   ©Úcreate_input)r   Úprompt_toolkit.input.defaultsr*   )r    r*   s     r!   r   zAppSession.input6   s1   € àŒ;ÐØBÐBÐBÐBÐBÐBà&˜,™.œ.ˆDŒKØŒ{Ðr#   r
   c                óH   — | j         €ddlm}  |¦   «         | _         | j         S )Nr   ©Úcreate_output)r   Úprompt_toolkit.output.defaultsr.   )r    r.   s     r!   r   zAppSession.output>   s1   € àŒ<ÐØDÐDÐDÐDÐDÐDà(˜=™?œ?ˆDŒLØŒ|Ðr#   ©NN)r   r   r   r   r   r   )r   r$   )r   r	   )r   r
   )	Ú__name__Ú
__module__Ú__qualname__Ú__doc__r"   r'   Úpropertyr   r   © r#   r!   r   r      s’   € € € € € ðð ð" CGð1ð 1ð 1ð 1ð 1ð/ð /ð /ð /ð ðð ð ñ „Xðð ðð ð ñ „Xðð ð r#   r   Ú_current_app_session)ÚdefaultzContextVar[AppSession]r   c                 ó4   — t                                ¦   «         S r   )r7   Úgetr6   r#   r!   r   r   L   s   € Ý×#Ò#Ñ%Ô%Ð%r#   úApplication[Any]c                 óp   — t                                ¦   «         } | j        | j        S ddlm}  |¦   «         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)r7   r:   r   Údummyr=   )Úsessionr=   s     r!   r   r   P   sF   € õ& #×&Ò&Ñ(Ô(€GØ„{ÐØŒ{Ðà'Ð'Ð'Ð'Ð'Ð'àÐÑÔÐr#   úApplication[Any] | Nonec                 óB   — t                                ¦   «         } | j        S )zj
    Get the current active (running) Application, or return `None` if no
    application is running.
    ©r7   r:   r   )r?   s    r!   r   r   l   s   € õ
 #×&Ò&Ñ(Ô(€GØŒ;Ðr#   r   úGenerator[None, None, None]c              #  óˆ   K  — t                                ¦   «         }|j        }| |_        	 dV — ||_        dS # ||_        w xY 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.
    NrB   )r   r?   Úprevious_apps      r!   r   r   u   sS   è è € õ #×&Ò&Ñ(Ô(€Gà”;€LØ€G„Kð#Øˆˆˆà"ˆŒˆˆølˆŒÐ"Ð"Ð"Ð"s	   «8 ¸	ANr   r   r   r   ú!Generator[AppSession, None, None]c              #  ó0  K  — | €t          ¦   «         j        } |€t          ¦   «         j        }t          | |¬¦  «        }t                               |¦  «        }	 |V — t                               |¦  «         dS # t                               |¦  «         w xY w)z§
    Create a separate AppSession.

    This is useful if there can be multiple individual ``AppSession``'s going
    on. Like in the case of a Telnet/SSH server.
    N©r   r   )r   r   r   r   r7   ÚsetÚreset)r   r   r?   Útokens       r!   r   r   ‹   s˜   è è € ð$ €}ÝÑ!Ô!Ô(ˆØ€~Ý Ñ"Ô"Ô*ˆõ ˜u¨VÐ4Ñ4Ô4€Gå ×$Ò$ WÑ-Ô-€Eð*Øˆˆˆå×"Ò" 5Ñ)Ô)Ð)Ð)Ð)øÕ×"Ò" 5Ñ)Ô)Ð)Ð)øøøs   ÁA9 Á9Bc               #  ó®   K  — ddl m}  ddlm}  | d¬¦  «        } |d¬¦  «        }t	          ||¬¦  «        5 }|V — ddd¦  «         dS # 1 swxY w Y   dS )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('>')
    r   r)   r-   T)Úalways_prefer_ttyrH   N)r+   r*   r/   r.   r   )r*   r.   r   r   Úapp_sessions        r!   r   r   ¬   sÐ   è è € ð  ;Ð:Ð:Ð:Ð:Ð:Ø<Ð<Ð<Ð<Ð<Ð<àˆL¨4Ð0Ñ0Ô0€EØˆ]¨TÐ2Ñ2Ô2€Få	 %°Ð	7Ñ	7Ô	7ð ¸;ØÐÐÐðð ð ñ ô ð ð ð ð ð ð ð øøøð ð ð ð ð ð s   ¸A
Á
AÁA)r   r   )r   r;   )r   r@   )r   r;   r   rC   r0   )r   r   r   r   r   rF   )r   rF   )Ú
__future__r   Ú
contextlibr   Úcontextvarsr   Útypingr   r   r   Úprompt_toolkit.input.baser	   Úprompt_toolkit.output.baser
   Úapplicationr   Ú__all__r   r7   Ú__annotations__r   r   r   r   r   r   r6   r#   r!   ú<module>rX      s»  ðØ "Ð "Ð "Ð "Ð "Ð "Ð "à %Ð %Ð %Ð %Ð %Ð %Ø "Ð "Ð "Ð "Ð "Ð "Ø 0Ð 0Ð 0Ð 0Ð 0Ð 0Ð 0Ð 0Ð 0Ð 0àð )Ø/Ð/Ð/Ð/Ð/Ð/Ø1Ð1Ð1Ð1Ð1Ð1à(Ð(Ð(Ð(Ð(Ð(ðð ð €ð,ð ,ð ,ð ,ð ,ñ ,ô ,ð ,ð^ 0:¨zØ J J¡L¤Lð0ñ 0ô 0Ð ð ð ð ñ ð
&ð &ð &ð &ðð ð ð ð8ð ð ð ð ð#ð #ð #ñ „ð#ð* à8<ð*ð *ð *ð *ñ „ð*ð@ ðð ð ñ „ðð ð r#   