unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: 24401@debbugs.gnu.org
Subject: bug#24401: python-shell-completion-native-try returns incorrect results with python 3.5.2
Date: Sat, 29 Oct 2016 10:12:54 -0400	[thread overview]
Message-ID: <52f53422-600a-d20f-4933-403a70f83dc7@gmail.com> (raw)
In-Reply-To: <184c70a4-edba-b253-8d7b-2c15d67dacfc@live.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1213 bytes --]

On 2016-09-10 00:00, Clément Pit--Claudel wrote:
> On 2016-09-09 19:30, Noam Postavsky wrote:
>> On Fri, Sep 9, 2016 at 7:07 PM, Clément Pit--Claudel 
>> <clement.pitclaudel@live.com> wrote:
>>> Hi all,
>>>
>>> Calling ‘run-python’ in ‘emacs -Q’ with ‘python-shell-interpreter’
>>> set to "python3", I get the following warning:
>>>
>>> Warning (python): Your ‘python-shell-interpreter’ doesn’t seem to
>>> support readline, yet ‘python-shell-completion-native’ was t and
>>> "python3" is not part of the
>>> ‘python-shell-completion-native-disabled-interpreters’ list. Native
>>> completions have been disabled locally.
>>>
>>> This warning is specific to Python 3 (it doesn't happen with Python
>>> 2.7). Additionally, the warning is spurious; native completion
>>> works fine.  This whole feature is new in Emacs 25.
>>
>> I'm not familiar enough with Python tooling to say much about this, 
>> but it seems similar (maybe identical) to #22897?
> 
> You're right. Why do I never find these duplicates?
> Does anyone object to the proposed fix?

If no one objects, I'll push the attached patch to master tomorrow (or should it go to emacs-25?)

Clément.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1.2: 0001-python.el-Fix-detection-of-native-completion-in-Pyth.patch --]
[-- Type: text/x-diff; name="0001-python.el-Fix-detection-of-native-completion-in-Pyth.patch", Size: 1230 bytes --]

From 9dd2c4867966d39d621d4862957b90dcc39fbdf0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Cl=C3=A9ment=20Pit--Claudel?= <clement.pitclaudel@live.com>
Date: Wed, 26 Oct 2016 22:46:28 -0400
Subject: [PATCH] python.el: Fix detection of native completion in Python 3
 (bug #24401)

With Python 3.5, (python-shell-completion-native-get-completions ... "")
would return an empty list, causing python.el to think that native
completion was unavailable.

* lisp/progmodes/python.el (python-shell-completion-native-try): Use "_"
  to check whether native completion is available instead of "".
---
 lisp/progmodes/python.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/progmodes/python.el b/lisp/progmodes/python.el
index ad69f87..290cdc8 100644
--- a/lisp/progmodes/python.el
+++ b/lisp/progmodes/python.el
@@ -3318,7 +3318,7 @@ python-shell-completion-native-try
          python-shell-completion-native-try-output-timeout))
     (python-shell-completion-native-get-completions
      (get-buffer-process (current-buffer))
-     nil "")))
+     nil "_")))
 
 (defun python-shell-completion-native-setup ()
   "Try to setup native completion, return non-nil on success."
-- 
2.7.4


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-10-29 14:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 23:07 bug#24401: python-shell-completion-native-try returns incorrect results with python 3.5.2 Clément Pit--Claudel
2016-09-09 23:30 ` Noam Postavsky
2016-09-10  4:00   ` Clément Pit--Claudel
2016-10-27  1:34     ` Lukas Juhrich
2016-10-27  3:35       ` Clément Pit--Claudel
2016-10-27  3:55       ` Clément Pit--Claudel
2016-10-29 14:12     ` Clément Pit--Claudel [this message]
2016-10-29 14:34       ` Eli Zaretskii
2016-10-29 15:03         ` Clément Pit--Claudel
2016-10-29 15:08           ` Eli Zaretskii
2016-10-31 12:38             ` Clément Pit--Claudel
2016-11-01  0:30               ` npostavs
2016-11-05  1:59                 ` npostavs
2016-11-05  3:28                   ` Clément Pit--Claudel
2016-11-29 16:38 ` bug#24401: Davor Rotim
2016-11-29 17:21   ` bug#24401: Clément Pit--Claudel
2016-11-29 20:27     ` bug#24401: Clément Pit--Claudel
2016-11-29 20:40 ` bug#24401: Davor Rotim
2016-11-29 22:35   ` bug#24401: Clément Pit--Claudel
2016-11-30  9:39 ` bug#24401: Davor Rotim
2016-11-30 14:22   ` bug#24401: Noam Postavsky
2016-11-30 15:09 ` bug#24401: Davor Rotim
2016-12-01  2:57   ` bug#24401: Clément Pit--Claudel
2016-12-01  8:47 ` bug#24401: Davor Rotim
2016-12-01 14:28   ` bug#24401: Clément Pit--Claudel
2016-12-02 16:31   ` bug#24401: Clément Pit--Claudel
2016-12-01 20:23 ` bug#24401: Davor Rotim
2016-12-01 20:40   ` bug#24401: Clément Pit--Claudel
2016-12-01 21:29 ` bug#24401: Davor Rotim
2016-12-01 21:45   ` bug#24401: Clément Pit--Claudel
2016-12-02  7:22     ` bug#24401: Eli Zaretskii
2016-12-02 17:13 ` bug#24401: Davor Rotim
2016-12-02 21:24   ` bug#24401: Clément Pit--Claudel
2016-12-02 21:51 ` bug#24401: Davor Rotim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52f53422-600a-d20f-4933-403a70f83dc7@gmail.com \
    --to=clement.pit@gmail.com \
    --cc=24401@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).