From: William Henney <whenney@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>,
emacs-org <emacs-orgmode@gnu.org>,
Florian Lindner <mailinglists@xgm.de>
Subject: Re: Problem with python session
Date: Wed, 12 Oct 2016 23:10:30 -0500 [thread overview]
Message-ID: <CAKchnZOet4aCAPRoADBbBcuhRDZ4AemzDy2KjfpzUmZF2OoJHw@mail.gmail.com> (raw)
In-Reply-To: <87a8earifk.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
Yep, I agree. This is a wart in the vanilla python REPL, and org-mode can't
really do much about it. Except maybe warn people.
As John noted, this is less of a problem if you use ipython as your REPL.
I think it is enough to just do
#+BEGIN_SRC emacs-lisp
(setq org-babel-python-command "ipython")
#+END_SRC
but I haven't tested this extensively since, as I mentioned, I prefer to
use Greg Sexton's ob-ipython instead. This integrates with the Jupyter
kernel by sending JSON to a web socket, rather than just pasting the source
block into a buffer, and that seems to be a more robust approach.
Will
On Tue, Oct 11, 2016 at 10:53 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > I am not sure it makes sense to change anything for this.
>
> Noted. Thank you for the feedback.
>
> Regards,
>
> --
> Nicolas Goaziou
>
>
--
Dr William Henney, Instituto de Radioastronomía y Astrofísica,
Universidad Nacional Autónoma de México, Campus Morelia
[-- Attachment #2: Type: text/html, Size: 1818 bytes --]
prev parent reply other threads:[~2016-10-13 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 12:41 Problem with python session Florian Lindner
2016-10-06 17:54 ` William Henney
2016-10-09 9:30 ` Nicolas Goaziou
2016-10-10 18:40 ` John Kitchin
2016-10-11 15:53 ` Nicolas Goaziou
2016-10-13 4:10 ` William Henney [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKchnZOet4aCAPRoADBbBcuhRDZ4AemzDy2KjfpzUmZF2OoJHw@mail.gmail.com \
--to=whenney@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=mailinglists@xgm.de \
/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/org-mode.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).