From: Kyle Meyer <kyle@kyleam.com>
To: Roger Mason <rmason@mun.ca>, Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Troublesome python block
Date: Wed, 11 Oct 2017 12:13:52 -0400 [thread overview]
Message-ID: <87y3ohd5mn.fsf@kyleam.com> (raw)
In-Reply-To: <y65vajlk8pc.fsf@mun.ca>
Hello,
Roger Mason <rmason@mun.ca> writes:
> This python block:
[...]
> produces this output:
>
> #+RESULTS:
> #+begin_example
> Python 2.7.13 (default, Jul 2 2017, 01:20:25)
> [GCC 4.2.1 Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)] on freebsd10
> Type "help", "copyright", "credits" or "license" for more information.
> python.el: native completion setup loaded
[...]
> Any help in debugging this will be much appreciated.
ob-python sessions have been broken to some degree for quite some time.
See, e.g., https://lists.gnu.org/archive/html/emacs-orgmode/2015-03/msg00540.html
I dropped my attempt to fix it because 1) I was still having trouble
getting a complete understanding of what the issue was and 2) I didn't
have the motivation to spend time digging deeper because I don't use
ob-python (and in general am not a heavy Org-Babel user). Perhaps you
or some other ob-python user could help make ob-python sessions more
robust?
In the meantime, you could try ob-ipython (https://github.com/gregsexton/ob-ipython).
Looking at the README, it sounds like ob-python's problems were one of
the author's motivations for writing the library.
--
Kyle
next prev parent reply other threads:[~2017-10-11 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 15:25 Troublesome python block Roger Mason
2017-10-11 16:13 ` Kyle Meyer [this message]
2017-10-11 16:35 ` Kaushal Modi
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=87y3ohd5mn.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=rmason@mun.ca \
/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.