From: "Андрей Парамонов" <cmr.pent@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 28580@debbugs.gnu.org
Subject: bug#28580: python.el: native completion setup failed
Date: Sun, 24 Sep 2017 19:56:39 +0300 [thread overview]
Message-ID: <CAC4Co6OeA--HnpAeeAZVx8k7MNquFn9+_CE7a3MwhjAuzHzp=g@mail.gmail.com> (raw)
In-Reply-To: <87lgl4m5uo.fsf@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Hi Noam,
and thank you for a quick reply!
2017-09-24 19:14 GMT+03:00 Noam Postavsky <npostavs@users.sourceforge.net>:
> > It is expected that Python completion works out-of-the-box, without
> > warnings.
>
> Seems to be impossible, unfortunately. Does this commentary from
> python.el help?
>
> ;; If your Python installation lacks readline (like CPython for
> ;; Windows), installing pyreadline (URL
> ;; `http://ipython.org/pyreadline.html') should suffice. To
> ;; troubleshoot why you are not getting any completions, you can try the
> ;; following in your Python shell:
> ;; >>> import readline, rlcompleter
>
> ;; If you see an error, then you need to either install pyreadline or
> ;; setup custom code that avoids that dependency.
>
It didn't help, unfortunately: I was indeed missing pyreadline, but
installing it from conda repo made no difference :-(
Neither did using "-i -u" as interactive Python arg.
I vaguely remember this working with older Pythons -- what could probably
change?
Best wishes,
Andrey Paramonov
[-- Attachment #2: Type: text/html, Size: 1754 bytes --]
next prev parent reply other threads:[~2017-09-24 16:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 15:56 bug#28580: python.el: native completion setup failed Андрей Парамонов
2017-09-24 16:14 ` Noam Postavsky
2017-09-24 16:56 ` Андрей Парамонов [this message]
2017-09-24 17:51 ` Noam Postavsky
2017-09-24 18:02 ` Андрей Парамонов
2017-09-24 18:09 ` Noam Postavsky
2017-09-24 18:16 ` Андрей Парамонов
2017-09-24 19:39 ` Noam Postavsky
2017-09-24 19:57 ` Андрей Парамонов
2017-09-24 20:06 ` Noam Postavsky
2017-09-24 20:19 ` Андрей Парамонов
2017-09-24 20:30 ` Noam Postavsky
2017-09-24 20:34 ` Андрей Парамонов
2017-09-24 21:00 ` Noam Postavsky
2017-09-24 21:08 ` Андрей Парамонов
2017-09-24 21:31 ` Noam Postavsky
2017-09-24 21:37 ` Андрей Парамонов
2017-10-03 4:01 ` Noam Postavsky
2017-10-12 19:40 ` Noam Postavsky
2017-10-13 3:28 ` Noam Postavsky
2017-10-15 18:23 ` Noam Postavsky
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='CAC4Co6OeA--HnpAeeAZVx8k7MNquFn9+_CE7a3MwhjAuzHzp=g@mail.gmail.com' \
--to=cmr.pent@gmail.com \
--cc=28580@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.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).