emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	Gary Oberbrunner <garyo@oberbrunner.com>
Subject: Re: Fwd: run python from org, draft
Date: Fri, 29 Mar 2013 10:47:17 -0600	[thread overview]
Message-ID: <87620arw4q.fsf@gmail.com> (raw)
In-Reply-To: <878v566up9.fsf@gmail.com> (Eric Schulte's message of "Fri, 29 Mar 2013 10:23:35 -0600")

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

> As we've proven a couple of times now, Python session are broken with
> the newest version of Emacs (since the upstream change to an entirely
> new python.el implementation).

I've just pushed up a fix to ob-python.el so that sessions should now
work with the latest version of Emacs.  I hope this clears up some of
the miss-understandings surrounding ob-python.

Here is a quick example usage.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: example.org --]
[-- Type: text/x-org, Size: 468 bytes --]

#+Title: Python Sessions

Works with an un-named session.
#+begin_src python :session
  x = 1 + 2
  x
#+end_src

#+RESULTS:
: 3

#+begin_src python :session
  x
#+end_src

#+RESULTS:
: 3

Works with a named session.
#+begin_src python :session foo
  x = 9
  x
#+end_src

#+RESULTS:
: 9

#+begin_src python :session foo
  x
#+end_src

#+RESULTS:
: 9

Notice that the un-named session still has the desired value.
#+begin_src python :session
x
#+end_src

#+RESULTS:
: 3

[-- Attachment #3: Type: text/plain, Size: 46 bytes --]


-- 
Eric Schulte
http://cs.unm.edu/~eschulte

  reply	other threads:[~2013-03-29 16:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 21:55 run python from org, draft Andreas Röhler
     [not found] ` <CAFChFyjZyxcnH1_jSWEUgXNkvJ0c3F8f4ojQa_EtPov2TjtziQ@mail.gmail.com>
2013-03-29 12:11   ` Fwd: " Gary Oberbrunner
2013-03-29 14:47     ` Andreas Röhler
2013-03-29 14:57       ` John Hendy
2013-03-29 15:09         ` Eric Schulte
2013-03-29 15:29           ` Andreas Röhler
2013-03-29 16:20             ` Eric Schulte
2013-03-29 16:49               ` Andreas Röhler
2013-03-29 16:59                 ` Eric Schulte
2013-03-29 18:33                   ` Evan Misshula
2013-03-29 18:50                     ` Eric Schulte
2013-03-29 19:04                       ` Evan Misshula
     [not found]             ` <CAFChFyhRbz6hh-NyOZTfdKJcTPh=F3J=07k2fR9p+A9Wig_pRA@mail.gmail.com>
2013-03-29 20:10               ` Fwd: " Gary Oberbrunner
2013-03-29 20:58                 ` Andreas Röhler
2013-03-31 20:04                   ` Gary Oberbrunner
2013-03-29 15:35           ` John Hendy
     [not found]             ` <CAFChFyhOrPVS2E5CE9H2+zX5TFV4D-themQbjx2DaSx-WmG14g@mail.gmail.com>
2013-03-29 20:11               ` Fwd: " Gary Oberbrunner
2013-03-29 15:50           ` John Hendy
2013-03-29 16:23             ` Eric Schulte
2013-03-29 16:47               ` Eric Schulte [this message]
2013-03-29 19:06                 ` Andreas Röhler
2013-03-29 20:04                 ` Andreas Röhler
2013-03-29 19:59           ` Gary Oberbrunner
2013-03-29 20:15             ` Andreas Röhler
2013-03-29 20:25             ` Eric Schulte
2013-03-29 20:45               ` Gary Oberbrunner
2013-03-29 21:13                 ` Eric Schulte

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=87620arw4q.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=garyo@oberbrunner.com \
    --cc=jw.hendy@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).