From: Ken Mankoff <mankoff@gmail.com>
To: Org-mode mailing list <emacs-orgmode@gnu.org>
Cc: John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Org + Elpy Python + IPython
Date: Tue, 20 May 2014 12:47:48 -0400 [thread overview]
Message-ID: <m24n0kieh7.fsf@gmail.com> (raw)
In-Reply-To: <m2eh05gex9.fsf@gmail.com>
Addendum to this old thread:
On 2014-05-07 at 22:52, Ken Mankoff <mankoff@gmail.com> wrote:
> FYI Org + Elpy + IPython all play nicely now.
>
> There have been some previous posts about people (me included) having
> trouble using the full IPython stack in Org Mode. Some of those
> problems were limited to when using sessions, and others only if
> trying to take full advantage of the nice Python support provided by
> Elpy (enabled via the (elpy-use-ipython) command).
>
> I think the primary issue was Org text analysis on the >>> prompt which
> in IPython becomes "In [n]:". This is solved with the "--classic" flag
> to ipython.
>
> With this setup:
>
> (setq org-babel-python-command "ipython --pylab=qt4 --pdb --nosep --classic --no-banner --no-confirm-exit")
>
> I now have Org, Python, IPython, and Elpy (including
> (elpy-use-ipython)) all running together in session and non-session
> mode.
ipython --classic appears to let IPython work properly with Org, but it
does not. There are some nefarious bugs. For example, the second
indented for loop (foo, bar) never runs if the interpreter is "ipython
--classic", but runs properly for "python".
for n in [1,2]:
print n
for a in ['a','b']:
print a
for f in ['foo','bar']:
print f
It appears that IPython munges empty lines differently than python. I've
tried the " --no-autoindent" and "--no-pprint" and the blank line still
causes problems. Anyway, I recommend sticking with plain Python which
works in all code I've tried both session and non-session.
-k.
next prev parent reply other threads:[~2014-05-20 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 2:52 Org + Elpy Python + IPython Ken Mankoff
2014-05-08 6:32 ` Puneeth Chaganti
2014-05-20 16:47 ` Ken Mankoff [this message]
2014-05-20 20:23 ` Ken Mankoff
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=m24n0kieh7.fsf@gmail.com \
--to=mankoff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).