Hello, Roger Mason <rma...@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
