argcomplete 3.1.0__tar.gz → 3.1.2__tar.gz

{argcomplete-3.1.0 → argcomplete-3.1.2}/Changes.rst

@@ -1,3 +1,15 @@
+Changes for v3.1.2 (2023-09-16)
+===============================
+
+-  Ensure Python 3.12+ compatibility in check_console_script (#448)
+
+Changes for v3.1.1 (2023-06-11)
+===============================
+
+-  Search through asdf shims
+
+-  Use \` as escape character in PowerShell (#434)
+
 Changes for v3.1.0 (2023-06-10)
 ===============================
 

{argcomplete-3.1.0/argcomplete.egg-info → argcomplete-3.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: argcomplete
-Version: 3.1.0
+Version: 3.1.2
 Summary: Bash tab completion for argparse
 Home-page: https://github.com/kislyuk/argcomplete
 Author: Andrey Kislyuk
@@ -33,9 +33,15 @@ Classifier: Topic :: System :: Shells
 Classifier: Topic :: Terminals
 Requires-Python: >=3.6
 Description-Content-Type: text/x-rst
-Provides-Extra: test
 License-File: LICENSE.rst
 License-File: NOTICE
+Requires-Dist: importlib-metadata<7,>=0.23; python_version < "3.8"
+Provides-Extra: test
+Requires-Dist: coverage; extra == "test"
+Requires-Dist: pexpect; extra == "test"
+Requires-Dist: wheel; extra == "test"
+Requires-Dist: ruff; extra == "test"
+Requires-Dist: mypy; extra == "test"
 
 argcomplete - Bash/zsh tab completion for argparse
 ==================================================
@@ -268,7 +274,7 @@ multiple Python versions on the same system, the version being used to run the s
 
 If you choose not to use global completion, or ship a completion module that depends on argcomplete, you must register
 your script explicitly using ``eval "$(register-python-argcomplete my-python-app)"``. Standard completion module
-registration roules apply: namely, the script name is passed directly to ``complete``, meaning it is only tab completed
+registration rules apply: namely, the script name is passed directly to ``complete``, meaning it is only tab completed
 when invoked exactly as it was registered. In the above example, ``my-python-app`` must be on the path, and the user
 must be attempting to complete it by that name. The above line alone would **not** allow you to complete
 ``./my-python-app``, or ``/path/to/my-python-app``.

{argcomplete-3.1.0 → argcomplete-3.1.2}/README.rst

@@ -229,7 +229,7 @@ multiple Python versions on the same system, the version being used to run the s
 
 If you choose not to use global completion, or ship a completion module that depends on argcomplete, you must register
 your script explicitly using ``eval "$(register-python-argcomplete my-python-app)"``. Standard completion module
-registration roules apply: namely, the script name is passed directly to ``complete``, meaning it is only tab completed
+registration rules apply: namely, the script name is passed directly to ``complete``, meaning it is only tab completed
 when invoked exactly as it was registered. In the above example, ``my-python-app`` must be on the path, and the user
 must be attempting to complete it by that name. The above line alone would **not** allow you to complete
 ``./my-python-app``, or ``/path/to/my-python-app``.

{argcomplete-3.1.0 → argcomplete-3.1.2}/argcomplete/_check_console_script.py

@@ -39,7 +39,8 @@ def main():
 
     # The importlib_metadata backport returns a tuple of entry point objects
     # whereas the official library returns a SelectableGroups object
-    if not use_entry_points_backport:
+    # Python 3.12+ behaves like the importlib_metadata backport
+    if not use_entry_points_backport and sys.version_info < (3, 12):
         entry_points = entry_points["console_scripts"] # type:ignore
 
     entry_points = [ep for ep in entry_points \

{argcomplete-3.1.0 → argcomplete-3.1.2}/argcomplete/bash_completion.d/_python-argcomplete

@@ -57,12 +57,12 @@ __python_argcomplete_upshift_bash_rematch() {
 
 # This function scans the beginning of an executable file provided as the first
 # argument ($1) for certain indicators, specified by the second argument ($2),
-# or the "target".  There are three possible targets: "interpreter",
+# or the "target". There are three possible targets: "interpreter",
 # "magic_string", and "easy_install". If the target is "interpreter", the
 # function matches the interpreter line, alongside any optional interpreter
 # arguments. If the target is "magic_string", a match is attempted for the
-# "PYTHON_ARGCOMPLETE_OK" magic string, indicating that the file should be
-# searched.  If the target is "easy_install", the function matches either
+# "PYTHON_ARGCOMPLETE_OK" magic string, indicating that the file should be run
+# to get completions. If the target is "easy_install", the function matches either
 # "PBR Generated" or any of the "EASY-INSTALL" scripts (either SCRIPT,
 # ENTRY-SCRIPT, or DEV-SCRIPT). In all cases, only the first kilobyte of
 # the file is searched. The regex matches are returned in BASH_REMATCH,
@@ -88,6 +88,7 @@ __python_argcomplete_scan_head() {
     case "$target" in
             magic_string) regex='PYTHON_ARGCOMPLETE_OK' ;;
             easy_install) regex="(PBR Generated)|(EASY-INSTALL-(SCRIPT|ENTRY-SCRIPT|DEV-SCRIPT))" ;;
+            asdf) regex="asdf exec " ;;
             interpreter) regex='^#!(.*)$' ;;
     esac
 
@@ -170,6 +171,9 @@ _python_argcomplete_global() {
         if (__python_argcomplete_which pyenv && [[ "$SCRIPT_NAME" = $(pyenv root)/shims/* ]]) >/dev/null 2>&1; then
             local SCRIPT_NAME=$(pyenv which "$executable")
         fi
+        if (__python_argcomplete_which asdf && __python_argcomplete_scan_head_noerr "$SCRIPT_NAME" asdf) >/dev/null 2>&1; then
+            local SCRIPT_NAME=$(asdf which "$executable")
+        fi
         if __python_argcomplete_scan_head_noerr "$SCRIPT_NAME" magic_string; then
             ARGCOMPLETE=1
         elif __python_argcomplete_scan_head_noerr "$SCRIPT_NAME" interpreter; then

{argcomplete-3.1.0 → argcomplete-3.1.2}/argcomplete/finders.py

@@ -519,8 +519,14 @@ class CompletionFinder(object):
             special_chars = ""
             completions = [c.replace("'", r"'\''") for c in completions]
 
+        # PowerShell uses ` as escape character.
+        if os.environ.get("_ARGCOMPLETE_SHELL") == "powershell":
+            escape_char = '`'
+            special_chars = special_chars.replace('`', '')
+        else:
+            escape_char = "\\"
         for char in special_chars:
-            completions = [c.replace(char, "\\" + char) for c in completions]
+            completions = [c.replace(char, escape_char + char) for c in completions]
 
         if self.append_space:
             # Similar functionality in bash was previously turned off by supplying the "-o nospace" option to complete.

{argcomplete-3.1.0 → argcomplete-3.1.2}/argcomplete/shell_integration.py

@@ -1,4 +1,3 @@
-#!/usr/bin/env python
 # Copyright 2012-2023, Andrey Kislyuk and argcomplete contributors. Licensed under the terms of the
 # `Apache License, Version 2.0 <http://www.apache.org/licenses/LICENSE-2.0>`_. Distribution of the LICENSE and NOTICE
 # files with source copies of this package and derivative works is **REQUIRED** as specified by the Apache License.
@@ -105,13 +104,13 @@ Register-ArgumentCompleter -Native -CommandName %(executable)s -ScriptBlock {
     $env:_ARGCOMPLETE = 1
     $env:_ARGCOMPLETE_SUPPRESS_SPACE = 0
     $env:_ARGCOMPLETE_IFS = "`n"
+    $env:_ARGCOMPLETE_SHELL = "powershell"
     %(argcomplete_script)s 2>&1 | Out-Null
 
     Get-Content $completion_file | ForEach-Object {
         [System.Management.Automation.CompletionResult]::new($_, $_, "ParameterValue", $_)
     }
-    rm $completion_file
-    Remove-Item Env:\_ARGCOMPLETE_STDOUT_FILENAME, Env:\ARGCOMPLETE_USE_TEMPFILES, Env:\COMP_LINE, Env:\COMP_POINT, Env:\_ARGCOMPLETE, Env:\_ARGCOMPLETE_SUPPRESS_SPACE, Env:\_ARGCOMPLETE_IFS
+    Remove-Item $completion_file, Env:\_ARGCOMPLETE_STDOUT_FILENAME, Env:\ARGCOMPLETE_USE_TEMPFILES, Env:\COMP_LINE, Env:\COMP_POINT, Env:\_ARGCOMPLETE, Env:\_ARGCOMPLETE_SUPPRESS_SPACE, Env:\_ARGCOMPLETE_IFS, Env:\_ARGCOMPLETE_SHELL
 }
 """  # noqa: E501
 

{argcomplete-3.1.0 → argcomplete-3.1.2/argcomplete.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: argcomplete
-Version: 3.1.0
+Version: 3.1.2
 Summary: Bash tab completion for argparse
 Home-page: https://github.com/kislyuk/argcomplete
 Author: Andrey Kislyuk
@@ -33,9 +33,15 @@ Classifier: Topic :: System :: Shells
 Classifier: Topic :: Terminals
 Requires-Python: >=3.6
 Description-Content-Type: text/x-rst
-Provides-Extra: test
 License-File: LICENSE.rst
 License-File: NOTICE
+Requires-Dist: importlib-metadata<7,>=0.23; python_version < "3.8"
+Provides-Extra: test
+Requires-Dist: coverage; extra == "test"
+Requires-Dist: pexpect; extra == "test"
+Requires-Dist: wheel; extra == "test"
+Requires-Dist: ruff; extra == "test"
+Requires-Dist: mypy; extra == "test"
 
 argcomplete - Bash/zsh tab completion for argparse
 ==================================================
@@ -268,7 +274,7 @@ multiple Python versions on the same system, the version being used to run the s
 
 If you choose not to use global completion, or ship a completion module that depends on argcomplete, you must register
 your script explicitly using ``eval "$(register-python-argcomplete my-python-app)"``. Standard completion module
-registration roules apply: namely, the script name is passed directly to ``complete``, meaning it is only tab completed
+registration rules apply: namely, the script name is passed directly to ``complete``, meaning it is only tab completed
 when invoked exactly as it was registered. In the above example, ``my-python-app`` must be on the path, and the user
 must be attempting to complete it by that name. The above line alone would **not** allow you to complete
 ``./my-python-app``, or ``/path/to/my-python-app``.

{argcomplete-3.1.0 → argcomplete-3.1.2}/pyproject.toml

@@ -1,5 +1,5 @@
 [build-system]
-requires = ["setuptools>=67.7.2", "wheel", "setuptools_scm[toml]>=6.2"]
+requires = ["setuptools>=67.7.2", "setuptools_scm[toml]>=6.2"]
 build-backend = "setuptools.build_meta"
 
 [project]