From: Andrii Kolomoiets <andreyk.mad@gmail.com>
To: Pankaj Jangid <p4j@j4d.net>
Cc: 38734@debbugs.gnu.org
Subject: bug#38734: 27.0.60; C-c C-p Warning - 'python-shell-interpreter' doesn't seem to support readline ...
Date: Thu, 26 Dec 2019 10:37:23 +0200 [thread overview]
Message-ID: <m2blrv32kc.fsf@gmail.com> (raw)
In-Reply-To: <0100016f3c760750-841a72a8-98cf-4a5b-8ea4-eddbbd79cb44-000000@email.amazonses.com> (Pankaj Jangid's message of "Wed, 25 Dec 2019 09:49:25 +0000")
Pankaj Jangid <p4j@j4d.net> writes:
>>> In python-mode, when I pressed C-c C-p to launch Python shell it
>>> produced below warning. I am on MacOS Catalina 10.15.2. On MacOS
>>> terminal, the python-shell opens without any warning.
>> This happens when python uses a libedit based readline module, which
>> is the default on macOS.
> Yes. With homebrew version it is working fine. And since this is
> duplicate of 25753, I'll close this.
>
> I was wondering why the python shell is working fine in the native
> terminal. Are they not using readline?
Different version of readline is used.
This code is used to check readline version:
import readline; print(readline.__doc__)
Under homebrew python it says "Importing this module enables command
line editing using GNU readline.".
Under python shipped with macos it says "Importing this module enables
command line editing using libedit readline."
Commit b33808ce77ef15c1f233790a2c93d9db4cc588ab disable native
completions when libedit readline is detected.
next prev parent reply other threads:[~2019-12-26 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 17:17 bug#38734: 27.0.60; C-c C-p Warning - 'python-shell-interpreter' doesn't seem to support readline Pankaj Jangid
2019-12-25 8:34 ` Andrii Kolomoiets
2019-12-25 9:49 ` Pankaj Jangid
2019-12-26 8:37 ` Andrii Kolomoiets [this message]
2019-12-26 11:10 ` Pankaj Jangid
[not found] ` <m27e2kbuqn.fsf@j4d.net>
2019-12-25 11:42 ` Pankaj Jangid
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=m2blrv32kc.fsf@gmail.com \
--to=andreyk.mad@gmail.com \
--cc=38734@debbugs.gnu.org \
--cc=p4j@j4d.net \
/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).