From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode@gnu.org
Subject: setting options to python interpreter for a code block
Date: Wed, 11 Sep 2013 13:22:12 -0400 [thread overview]
Message-ID: <CAJ51ETpJZdU5M4-fNmsOu5T2mqQkcSgYzV1xDNSk3=e3QmXy-A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
Hi,
I am looking at a new strategy to capture stderr and exceptions in python
code blocks. Right now exceptions are not captured in the output, and
neither is stderr.
I made a little sandbox module that captures stdout, stderr, and exceptions
and then prints them all to stdout with some minor formatting. Here is an
example.
Say test.py has this content
#+BEGIN_SRC python
print 'hello'
print 4 + 6
import sys
print >>sys.stderr, 'message to stderr'
raise Exception('baboom')
#+END_SRC
When I use the sandbox, I get all the output on stdout like this.
#+BEGIN_SRC sh
python -m sandbox < test.py
# or cat test.py | python -m sandbox
#+END_SRC
#+RESULTS:
#+begin_example
--------------------------------------------------------------
hello
10
--------------------------------------------------------------
stderr:
message to stderr
--------------------------------------------------------------
Traceback (most recent call last):
File "/home/jkitchin/Dropbox/pycse/pycse/sandbox/sandbox.py", line 16, in
<module>
exec(content, ns_globals, ns_locals)
File "<string>", line 10, in <module>
Exception: baboom
#+end_example
So, I was wondering how to get this to happen in org-mode on a regular
python block. I think it could work if I could define a custom interpreter
for a particular block, e.g. python-sandbox that takes the codeblock on
stdin.
Is there some other way that I could do this? Thanks!
John
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
[-- Attachment #2: Type: text/html, Size: 2232 bytes --]
next reply other threads:[~2013-09-11 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 17:22 John Kitchin [this message]
2013-09-11 18:17 ` setting options to python interpreter for a code block Eric Schulte
2013-09-11 18:25 ` John Kitchin
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='CAJ51ETpJZdU5M4-fNmsOu5T2mqQkcSgYzV1xDNSk3=e3QmXy-A@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
/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).