emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: "Sebastian P. Luque" <spluque@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Python loops with ":results output"
Date: Tue, 21 Feb 2017 22:08:45 +0000	[thread overview]
Message-ID: <CAJ51ETrsecjz8N5UicDzDkZM1MO81Ki7WK04aJ=egiZFCNiOnQ@mail.gmail.com> (raw)
In-Reply-To: <87zihfxnyg.fsf@otaria.sebmel.org>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

The startup is a bit slower I find too. On the other hand I get the right
output, async execution, multiple inline images, and export to jupyter
notebooks with my scimax modifications.


On Tue, Feb 21, 2017 at 3:53 PM Sebastian P. Luque <spluque@gmail.com>
wrote:

> On Tue, 21 Feb 2017 08:58:59 -0500,
> John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>
> > On Mon, Feb 20, 2017 at 11:04 PM, Seb <spluque@gmail.com> wrote:
> >     #+BEGIN_SRC python :session :results output :exports results for i
> > in range(3):     print("Iter {0}".format(i))
>
> >     #+END_SRC
>
> > Try using ob-ipython. It doesn't have that issue for me.
>
> Thank you; unfortunately, this seems to work with Jupyter/Ipython
> kernels running as a service, which adds quite an overhead to the
> workflow.
>
> --
> Seb
>
>
> --
John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

[-- Attachment #2: Type: text/html, Size: 2122 bytes --]

      reply	other threads:[~2017-02-21 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21  4:04 Python loops with ":results output" Seb
2017-02-21 13:58 ` John Kitchin
2017-02-21 20:56   ` Sebastian P. Luque
2017-02-21 22:08     ` John Kitchin [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='CAJ51ETrsecjz8N5UicDzDkZM1MO81Ki7WK04aJ=egiZFCNiOnQ@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=spluque@gmail.com \
    /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).