U
    `»{jÀ  ã                   @  sÀ   U d Z ddlmZ ddlZddlmZ ddlZddlZddlmZ G dd„ dƒZ	ej
 d¡r¨zddlZW n ek
r†   e d	¡ Y nX e	ƒ Zd
ed< dddœdd„Znd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).
é    )ÚannotationsN)Úglob)ÚAnyc                   @  s4   e Zd ZdZddddœdd„Zdd	d
dœdd„ZdS )ÚFastFilesCompleterzFast file completer class.TÚboolÚNone)ÚdirectoriesÚreturnc                 C  s
   || _ d S ©N)r   )Úselfr   © r   úS/var/www/html/bwave/python/venv/lib/python3.8/site-packages/_pytest/_argcomplete.pyÚ__init__M   s    zFastFilesCompleter.__init__Ústrr   z	list[str])ÚprefixÚkwargsr	   c                 K  s¸   t j|dd … kr*tt j |¡t j ƒ}nd}g }g }d|krrd|k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__P   s    zFastFilesCompleter.__call__N)T)Ú__name__Ú
__module__Ú__qualname__Ú__doc__r   r"   r   r   r   r   r   J   s   r   Z_ARGCOMPLETEr   zFastFilesCompleter | NoneÚfilescompleterzargparse.ArgumentParserr   )Úparserr	   c                 C  s   t j| dd� d S )NF)Zalways_complete_options)ÚargcompleteÚautocomplete©r(   r   r   r   Útry_argcompletem   s    r,   c                 C  s   d S r
   r   r+   r   r   r   r,   r   s    )r&   Ú
__future__r   Úargparser   r   ÚsysÚtypingr   r   ÚenvironÚgetZargcomplete.completersr)   ÚImportErrorÚexitr'   Ú__annotations__r,   r   r   r   r   Ú<module>   s    @