a
    !f                     @   s   U d Z ddlZddlZddlZddlmZ ddlmZ ddlmZ ddlmZ G dd dZ	ej
d	rzddlZW n ey   ed
 Y n0 e	 Zee	 ed< ejddddZnejddddZdZdS )a  Allow bash-completion for argparse with argcomplete if installed.

Needs argcomplete>=0.5.6 for python 3.2/3.3 (older versions fail
to find the magic string, so _ARGCOMPLETE env. var is never set, and
this does not need special code).

Function try_argcomplete(parser) should be called directly before
the call to ArgumentParser.parse_args().

The filescompleter is what you normally would use on the positional
arguments specification, in order to get "dirname/" after "dirn<TAB>"
instead of the default "dirname ":

   optparser.add_argument(Config._file_or_dir, nargs='*').completer=filescompleter

Other, application specific, completers should go in the file
doing the add_argument calls as they need to be specified as .completer
attributes as well. (If argcomplete is not installed, the function the
attribute points to will not be used).

SPEEDUP
=======

The generic argcomplete script for bash-completion
(/etc/bash_completion.d/python-argcomplete.sh)
uses a python program to determine startup script generated by pip.
You can speed up completion somewhat by changing this script to include
  # PYTHON_ARGCOMPLETE_OK
so the python-argcomplete-check-easy-install-script does not
need to be called to find the entry point of the code and see if that is
marked  with PYTHON_ARGCOMPLETE_OK.

INSTALL/DEBUGGING
=================

To include this support in another application that has setup.py generated
scripts:

- Add the line:
    # PYTHON_ARGCOMPLETE_OK
  near the top of the main python entry point.

- Include in the file calling parse_args():
    from _argcomplete import try_argcomplete, filescompleter
  Call try_argcomplete just before parse_args(), and optionally add
  filescompleter to the positional arguments' add_argument().

If things do not work right away:

- Switch on argcomplete debugging with (also helpful when doing custom
  completers):
    export _ARC_DEBUG=1

- Run:
    python-argcomplete-check-easy-install-script $(which appname)
    echo $?
  will echo 0 if the magic line has been found, 1 if not.

- Sometimes it helps to find early on errors using:
    _ARGCOMPLETE=1 _ARC_DEBUG=1 appname
  which should throw a KeyError: 'COMPLINE' (which is properly set by the
  global argcomplete script).
    N)glob)Any)List)Optionalc                   @   s8   e Zd ZdZd
eddddZeeee ddd	Z	dS )FastFilesCompleterzFast file completer class.TN)directoriesreturnc                 C   s
   || _ d S N)r   )selfr    r   U/var/www/html/python-backend/venv/lib/python3.9/site-packages/_pytest/_argcomplete.py__init__L   s    zFastFilesCompleter.__init__)prefixkwargsr   c                 K   s   t j|dd  v r*tt j|t j }nd}g }g }d|vrrd|vrr|rX|d t jkrj|t|d  |d7 }|t| t|D ]*}t j|r|d7 }|	||d   q|S )N   r   *?z.*/)
osseplenpathdirnameextendr   sortedisdirappend)r
   r   r   Z
prefix_dir
completionZglobbedxr   r   r   __call__O   s    zFastFilesCompleter.__call__)T)
__name__
__module____qualname____doc__boolr   strr   r   r    r   r   r   r   r   I   s   r   Z_ARGCOMPLETEr   filescompleter)parserr   c                 C   s   t j| dd d S )NF)Zalways_complete_options)argcompleteautocompleter(   r   r   r   try_argcompletel   s    r,   c                 C   s   d S r	   r   r+   r   r   r   r,   q   s    )r$   argparser   sysr   typingr   r   r   r   environgetZargcomplete.completersr)   ImportErrorexitr'   __annotations__ArgumentParserr,   r   r   r   r   <module>   s"   ?