U
    d-                     @  s  U d dl mZ d dlZd dlmZ d dlmZ d dlmZm	Z	m
Z
mZ ernd dlmZ d dlmZ dd	lmZ d
ddddddgZG dd
 d
Zede dZded< d
dddZddddZddddZedddddZed$ddd d!d"dZed dd#dZdS )%    )annotationsN)contextmanager)
ContextVar)TYPE_CHECKINGAny	GeneratorOptional)Input)Output   )Application
AppSessionget_app_sessionget_appget_app_or_noneset_appcreate_app_sessioncreate_app_session_from_ttyc                   @  sV   e Zd ZdZdddddddZd	d
ddZedd
ddZedd
ddZdS )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Input | NoneOutput | NoneNoneinputoutputreturnc                 C  s   || _ || _d | _d S N)_input_outputapp)selfr   r    r    F/tmp/pip-unpacked-wheel-4x_7prb2/prompt_toolkit/application/current.py__init__*   s    zAppSession.__init__strr   c                 C  s   d| j dS )NzAppSession(app=))r   )r   r    r    r!   __repr__4   s    zAppSession.__repr__r	   c                 C  s$   | j d krddlm} | | _ | j S )Nr   create_input)r   prompt_toolkit.input.defaultsr(   )r   r(   r    r    r!   r   7   s    
zAppSession.inputr
   c                 C  s$   | j d krddlm} | | _ | j S )Nr   create_output)r   prompt_toolkit.output.defaultsr+   )r   r+   r    r    r!   r   ?   s    
zAppSession.output)NN)	__name__
__module____qualname____doc__r"   r&   propertyr   r   r    r    r    r!   r      s      
_current_app_session)defaultzContextVar[AppSession]r$   c                   C  s   t  S r   )r2   getr    r    r    r!   r   M   s    zApplication[Any]c                  C  s*   t  } | jdk	r| 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)r2   r4   r   dummyr5   )sessionr5   r    r    r!   r   Q   s
    
zApplication[Any] | Nonec                  C  s   t  } | jS )zj
    Get the current active (running) Application, or return `None` if no
    application is running.
    r2   r4   r   )r7   r    r    r!   r   m   s    zGenerator[(None, None, None)])r   r   c                 c  s,   t  }|j}| |_z
dV  W 5 ||_X dS )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.
    Nr8   )r   r7   Zprevious_appr    r    r!   r   v   s    
r   r   z!Generator[AppSession, None, None]r   c              	   c  sd   t jdkrtd| dkr"t j} |dkr2t j}t| |d}t|}z
|V  W 5 t	| X dS )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r   r   )
sysversion_infoRuntimeErrorr   r   r   r   r2   setreset)r   r   r7   tokenr    r    r!   r      s    


c               	   c  sN   ddl m}  ddlm} | dd}|dd}t||d}|V  W 5 Q R X 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)Zalways_prefer_ttyr;   N)r)   r(   r,   r+   r   )r(   r+   r   r   Zapp_sessionr    r    r!   r      s    

)NN)
__future__r   r<   
contextlibr   Zcontextvarsr   typingr   r   r   r   Zprompt_toolkit.input.baser	   Zprompt_toolkit.output.baser
   Zapplicationr   __all__r   r2   __annotations__r   r   r   r   r   r   r    r    r    r!   <module>   sB    / 	   