B
    ܇\                 @   s   d Z ddlmZ ddlmZ ddlmZ ddlZddlZddlmZ G dd deZ	ej
d	ryddlZW n ek
r   ed
 Y nX e	 Zdd Zn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 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).
    )absolute_import)division)print_functionN)globc               @   s"   e Zd ZdZdddZdd ZdS )	FastFilesCompleterzFast file completer classTc             C   s
   || _ d S )N)directories)selfr    r	   3lib/python3.7/site-packages/_pytest/_argcomplete.py__init__D   s    zFastFilesCompleter.__init__c             K   s   t jj|dd kr.tt j|t jj }nd}g }g }d|krxd|krx|r^|d t jjkrp|t|d  |d7 }|t| x6t|D ]*}t j|r|d7 }|	||d  qW |S )	z%only called on non option completions   Nr   *?z.*/)
ospathseplendirnameextendr   sortedisdirappend)r   prefixkwargsZ
prefix_dirZ
completionZglobbedxr	   r	   r
   __call__G   s    zFastFilesCompleter.__call__N)T)__name__
__module____qualname____doc__r   r   r	   r	   r	   r
   r   A   s   
r   Z_ARGCOMPLETEr   c             C   s   t j| dd d S )NF)Zalways_complete_options)argcompleteZautocomplete)parserr	   r	   r
   try_argcompleted   s    r$   c             C   s   d S )Nr	   )r#   r	   r	   r
   r$   j   s    )r!   Z
__future__r   r   r   r   sysr   objectr   environgetZargcomplete.completersr"   ImportErrorexitZfilescompleterr$   r	   r	   r	   r
   <module>7   s    
