g'dZddlZddlZddlmZGddZejdr0 ddlZn#e $rej dYnwxYweZ dZ dSd Z dZ dS) 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. argcomplete does not support python 2.5 (although the changes for that are minor). 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" 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). N)globc eZdZdZddZdZdS)FastFilesCompleterzFast file completer classTc||_dSN) directories)selfrs J/granary/edev/quantum/lib/python3.11/site-packages/_pytest/_argcomplete.py__init__zFastFilesCompleter.__init__Cs&c Jtjj|ddvr?ttj|tjjz}nd}g}g}d|vrId|vrE|dtjjkr%|t |dz|dz }|t |t|D]C}tj|r|dz }| ||dD|S) z%only called on non option completionsNr*?z.*/) ospathseplendirnameextendrsortedisdirappend)r prefixkwargs prefix_dir completionglobbedxs r __call__zFastFilesCompleter.__call__Fs 7;&* $ $RW__V44rw{BCCJJJ  f  F!2!2bzRW[((tFTM22333 cMFtF||$$$ . .Aw}}Q S   a n - - - -r N)T)__name__ __module__ __qualname____doc__r r"r r rrAs=''''r r _ARGCOMPLETErc.tj|dSr) argcomplete autocompleteparsers r try_argcompleter.as (((((r cdSrr'r,s r r.r.dsr ) r&sysrrrenvirongetargcomplete.completersr* ImportErrorexitfilescompleterr.r'r r r7s99v 2:>>.!! %%%%%  ''))N)))))&%%NNNs>AA