From: Jaan Altosaar <altosaar@princeton.edu>
To: 32042@debbugs.gnu.org
Subject: bug#32042: 26.1; python.el with ipython prompt leads to superfluous interactive shell output
Date: Tue, 10 Jul 2018 18:14:42 -0400 [thread overview]
Message-ID: <CADzm6z+FH1G=ZKP67DUg7_mhxEcrzjSh_8X48fDJd+EL=UJ9jw@mail.gmail.com> (raw)
In-Reply-To: <mailman.3332.1531166168.1292.bug-gnu-emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Thanks! It looks like it's the anaconda readline:
```
Python 3.6.6 |Anaconda custom (64-bit)| (default, Jun 28 2018, 11:07:29)
Type 'copyright', 'credits' or 'license' for more information
IPython 6.4.0 -- An enhanced Interactive Python. Type '?' for help.
>>> import readline; print(readline.__doc__); print(readline.__file__)
Importing this module enables command line editing using GNU readline.
/usr/local/anaconda3/lib/python3.6/site-packages/
readline.cpython-36m-darwin.so
```
I tried using gnureadline too but get the same broken output.
```
>>> import readline
>>> print(readline.__doc__); print(readline.__file__)
Importing this module enables command line editing using GNU readline.
/usr/local/anaconda3/lib/python3.6/site-packages/readline.py
>>> cat /usr/local/anaconda3/lib/python3.6/site-packages/readline.py
from gnureadline import *
from gnureadline import __doc__
```
On Monday, July 9, 2018, Noam Postavsky <npostavs@gmail.com> wrote:
> On 9 July 2018 at 08:59, Jaan Altosaar <altosaar@princeton.edu> wrote:
> > My bad! Reply alling to keep 32042@debbugs.gnu.org in cc. Hope this
> works—
>
> > Still getting the same broken output.
> >
> > Any other ideas?
>
> Can you show the result of the python expressions at the bottom of
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32042#19
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2091 bytes --]
next prev parent reply other threads:[~2018-07-10 22:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 20:13 bug#32042: 26.1; python.el with ipython prompt leads to superfluous interactive shell output Jaan Altosaar
2018-07-02 20:32 ` Noam Postavsky
2018-07-02 21:18 ` Jaan Altosaar
2018-07-03 0:45 ` Noam Postavsky
2018-07-09 12:59 ` Jaan Altosaar
2018-07-09 19:55 ` Noam Postavsky
[not found] ` <mailman.3332.1531166168.1292.bug-gnu-emacs@gnu.org>
2018-07-10 22:09 ` Jaan Altosaar
2018-07-10 22:36 ` Noam Postavsky
[not found] ` <mailman.3400.1531262228.1292.bug-gnu-emacs@gnu.org>
2018-07-10 22:51 ` Jaan Altosaar
2018-07-11 0:32 ` Noam Postavsky
2021-09-05 7:42 ` Lars Ingebrigtsen
2018-07-10 22:14 ` Jaan Altosaar [this message]
[not found] ` <mailman.2978.1530578768.1292.bug-gnu-emacs@gnu.org>
2018-07-06 19:21 ` jaan.altosaar
2018-07-07 14:43 ` Noam Postavsky
2018-07-07 16:42 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADzm6z+FH1G=ZKP67DUg7_mhxEcrzjSh_8X48fDJd+EL=UJ9jw@mail.gmail.com' \
--to=altosaar@princeton.edu \
--cc=32042@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.