GNU bug report logs - #68559
[PATCH] Improve Python shell completion

Previous Next

Full log

View this message in rfc822 format

From: kobarity <kobarity <at> gmail.com>
To: Liu Hui <liuhui1610 <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 68559 <at> debbugs.gnu.org
Subject: bug#68559: [PATCH] Improve Python shell completion
Date: Sun, 21 Jan 2024 18:34:53 +0900

Eli Zaretskii wrote:
> 
> > From: Liu Hui <liuhui1610 <at> gmail.com>
> > Date: Thu, 18 Jan 2024 12:48:37 +0800
> > 
> > Currently python-shell-completion-at-point doesn't respect the
> > delimiter setting of readline completer and always split the text,
> > resulting in poor completions when completers that don't need word
> > splitting, e.g. jedi[1], is used. This patch fixes the problem.
> > 
> > Meanwhile, this patch adds an option 'python-shell-readline-completer'
> > to make Python shell provide better completion experience (e.g.
> > completing function parameters, dictionary keys) by default if users
> > are using vanilla Python interpreter with jedi or using IPython, where
> > the completion support for IPython has been enhanced (e.g. showing
> > type annotations and function signatures).
> > 
> > BTW, I think it may make sense to move Python snippets to a separate
> > file to make them easier to be maintained.
> 
> Thanks.  Let's see what others think about this (I don't use Python
> enough to have an opinion that matters).

Thanks for the patch.  I have tried it and found it to be a very
powerful enhancement.

Is it possible to allow completion of keyword arguments in a
multi-line function call like the following?

#+begin_src python
re.split(
    'b',
    'abc',
    maxs
#+end_src

I am not sure if Python snippets should be separated.  Do other
language supports keep them separate?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.