From: Myles English <mylesenglish@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: python :session issues
Date: Wed, 06 Feb 2013 15:10:04 +0000 [thread overview]
Message-ID: <87r4ktiilv.fsf@gmail.com> (raw)
In-Reply-To: <CAJ51ETr+WXyDVTF7+eVTLpy78S51U-dH35Oh3DYNm6hkJnzPxg@mail.gmail.com>
Hi John,
John Kitchin writes:
> I have been trying to use the :session feature of babel for python code
> blocks. I have noticed a few things that might be areas for
> improvement. Some issues are related to what I think might be a need for
> sanitizing the code blocks and the output.
>
> I am using (insert (org-version)) 7.9.3a
> I am using python-mode 5.2 (more modern versions do not work with
> :session for me)
>
> The first small detail is illustrated here:
>
> #+BEGIN_SRC python :session
> a = 5
>
> b = 6
>
> print a + b
> #+END_SRC
>
> #+RESULTS:
> :
> : >>> >>> >>> 11
>
> In the output, there are three sets of >>>, due to the two empty
> lines. Compare this to
>
> #+BEGIN_SRC python :session
> a = 5
> b = 6
> print a + b
> #+END_SRC
>
> #+RESULTS:
> :
> : >>> 11
>
> I think it would be nice to sanitize the python code block sent to the
> interpreter to eliminate the empty lines, and avoid the multiple >>> in
> output. It would also be nice to have an option to not print those at
> all.
>
> The second issue is related. The following code does not work for me in
> :session, but it works fine as a standalone block. The issue is related
> to the presence of an empty line in the function definition. I like
> whitespace like this in functions sometimes for readability.
>
> #+BEGIN_SRC python :session
> def func(x):
> 'doc string'
>
> return x**2
>
> print func(2)
> #+END_SRC
>
> #+RESULTS:
> :
> : ... >>> File "<stdin>", line 1
> : return x**2
> : ^
> : IndentationError: unexpected indent
> : >>> None
>
> Removing the blank line works fine, but still has some non-pretty
> output.
>
> #+BEGIN_SRC python :session
> def func(x):
> 'doc string'
> return x**2
>
> print func(2)
> #+END_SRC
>
> #+RESULTS:
> :
> : ... ... >>> 4
>
> One of the ellipsis is due to the doc string.
> #+BEGIN_SRC python :session
> def func(x):
> return x**2
>
> print func(2)
> #+END_SRC
>
> #+RESULTS:
> :
> : ... >>> 4
>
> Interestingly, this did not work, because there is no empty line after
> the function definition. So, sanitizing could be tricky.
>
> #+BEGIN_SRC python :session
> def func(x):
> 'doc string'
> return x**2
> print func(2)
> #+END_SRC
>
> #+RESULTS:
> :
> : ... ... File "<stdin>", line 4
> : print func(2)
> : ^
> : SyntaxError: invalid syntax
>
> I think if there was a way to strip all the empty lines from the input,
> it would go a long way to making the output look like what I think most
> people would expect and want.
>
> Anyway, those are the examples I wanted to highlight in this
> post.
>
>
> 1. Do you see similar behavior, or is this a feature of my setup?
I haven't tried your examples (no time) but you would be able to tell if
it was a feature of your setup by making a minimum working example and
starting emacs with 'emacs -Q'. If you see the thread in the footnote
it contains such an example.
> 2. Is there any interest in sanitizing the input and output of a
> python :session to get prettier output? if so, Any hints on where to
> start with that?
I had some problems recently with :session, there was a short discussion[1],
and last I heard the maintainer of python-mode.el is looking into it.
Myles
Footnotes:
[1] https://lists.gnu.org/archive/html/emacs-orgmode/2013-01/msg00888.html
next prev parent reply other threads:[~2013-02-06 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 2:19 python :session issues John Kitchin
2013-02-06 15:10 ` Myles English [this message]
2013-02-06 15:17 ` John Kitchin
2013-02-07 16:54 ` Andreas Röhler
2013-02-07 21:53 ` Myles English
2013-02-08 9:23 ` Andreas Röhler
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=87r4ktiilv.fsf@gmail.com \
--to=mylesenglish@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).