a
    lc                     @   sF  U d dl Z d dlmZ d dlmZmZmZmZ zd dlm	Z	 W n e
y\   d dlm	Z	 Y n0 erd dlmZ d dlmZ ddlmZ g d	ZG d
d dZe	de dZe	d ed< edddZddddZed dddZeded dddZed!ed ed eeddf dddZeeeddf ddd ZdS )"    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                   @   s^   e Zd ZdZded ed ddddZe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.
    Nr   r	   inputoutputreturnc                 C   s   || _ || _d | _d S N)_input_outputapp)selfr   r    r   ^/var/www/html/django/DPS/env/lib/python3.9/site-packages/prompt_toolkit/application/current.py__init__,   s    zAppSession.__init__r   c                 C   s   d| j dS )NzAppSession(app=))r   )r   r   r   r   __repr__7   s    zAppSession.__repr__c                 C   s$   | j d u rddlm} | | _ | j S )Nr   create_input)r   prompt_toolkit.input.defaultsr#   )r   r#   r   r   r   r   :   s    
zAppSession.inputc                 C   s$   | j d u rddlm} | | _ | j S )Nr   create_output)r   prompt_toolkit.output.defaultsr&   )r   r&   r   r   r   r   B   s    
zAppSession.output)NN)__name__
__module____qualname____doc__r   r   strr!   propertyr   r   r   r   r   r   r      s    r   _current_app_session)defaultr   c                   C   s   t  S r   )r.   getr   r   r   r   r   P   s    r   zApplication[Any]c                  C   s*   t  } | jdu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)r.   r0   r   dummyr1   )sessionr1   r   r   r   r   T   s
    
r   c                  C   s   t  } | jS )zj
    Get the current active (running) Application, or return `None` if no
    application is running.
    r.   r0   r   )r3   r   r   r   r   p   s    r   )NNN)r   r   c                 c   s2   t  }|j}| |_zdV  W ||_n||_0 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.
    Nr4   )r   r3   Zprevious_appr   r   r   r   y   s    r   r   r	   r   c              	   c   sn   t jdkrtd| du r"t j} |du r2t j}t| |d}t|}z|V  W t	| nt	| 0 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   r.   setreset)r   r   r3   tokenr   r   r   r      s    

r   c                  c   sb   ddl m}  ddlm} | dd}|dd}t||d}|V  W d   n1 sT0    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)Zalways_prefer_ttyr7   N)r$   r#   r'   r&   r   )r#   r&   r   r   Zapp_sessionr   r   r   r      s    

r   )NN)r8   
contextlibr   typingr   r   r   r   contextvarsr   ImportErrorZ*prompt_toolkit.eventloop.dummy_contextvarsZprompt_toolkit.input.baser   Zprompt_toolkit.output.baser	   Zapplicationr   __all__r   r.   __annotations__r   r   r   r   r   r   r   r   r   r   <module>   s8   
0	 