GNU bug report logs - #28580
[w32] python.el: native completion setup failed

Previous Next

Package: emacs;

Reported by: Андрей Парамонов <cmr.pent <at> gmail.com>

Date: Sun, 24 Sep 2017 15:58:02 UTC

Severity: normal

Tags: fixed, patch

Merged with 22897, 24401, 30651

Found in versions 25.1, 25.1.50

Fixed in version 25.2

Done: Noam Postavsky <npostavs <at> users.sourceforge.net>

Bug is archived. No further changes may be made.

Full log


Message #38 received at 28580 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Андрей Парамонов
 <cmr.pent <at> gmail.com>
Cc: 28580 <at> debbugs.gnu.org
Subject: Re: bug#28580: python.el: native completion setup failed
Date: Sun, 24 Sep 2017 16:30:26 -0400
Андрей Парамонов <cmr.pent <at> gmail.com> writes:

> Bad news: the message
> Warning (python): Your ‘python-shell-interpreter’ doesn’t seem to
> support readline, yet ‘python-shell-completion-native-enable’ was t
> and "py" is not part of the
> ‘python-shell-completion-native-disabled-interpreters’ list.  Native
> completions have been disabled locally. 
> still appears when I M-x run-python
>
> Good news: python shell buffer now displays
>>>> python.el: native completion setup loaded
> after I eval the contents of t.py. Actually, it displays the message
> upon loading, and completion does work. I must have believed the
> warning rather than checked, after install of pyreadline.

Can you clarify, if you just run M-x run-python without doing anything
with "t.py" you see the "python.el: native completion setup loaded" or
the "python.el: native completion setup failed" message?

> Why the message appears? It tells that completion is disabled which
> is not true!

The "native" completion might still be disabled, and you're actually
using the "fallback" method.




This bug report was last modified 7 years and 80 days ago.

Previous Next


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