I think the issue here is that python users seem less likely (per user on average) to edit the related Org-mode support (i.e., ob-python.el) than users of some other languages which may be less popular in the large but have better Org-mode support.
Also, as a maintainer of Org-mode's code block support, I personally do not use Python. Best, Ken Mankoff <mank...@gmail.com> writes: > Hi John, > > Yes, you and others in that thread seem to be experiencing the same > problem, although there are also different issues discussed there. > > I'm a bit surprised... With the popularity of python I would expect more > org users to have run into this and it to be fixed, but perhaps it isn't as > widely used as I thought. Anyway, it is now usable even if the 'print' > statements don't show up. > > -k. > > > > On Tue, Jan 14, 2014 at 6:04 PM, John Hendy <jw.he...@gmail.com> wrote: > >> On Tue, Jan 14, 2014 at 7:38 AM, Ken Mankoff <mank...@gmail.com> wrote: >> > >> > I've seen various historical issues with :session but it seems I may >> have a >> > different problem. This is the latest org in emacs 24.3. If I do not have >> > :session, then everything works just fine. >> > >> >> This sounded familiar to me, so I googled around for Org mailing list >> discussions I was involved in related to python. Does this shed any >> new light? >> - https://www.mail-archive.com/emacs-orgmode@gnu.org/msg68542.html >> >> Seems that the discussion ended with the possibility that it was an >> emacs change to python.el, and not related to Org, but I'm not sure if >> any actions were ever taken regarding that. In any case, the >> discussion features a discrepancy between python behavior with >> `:session name` and without, so it seemed like a possible candidate to >> pass along! >> >> >> >> Best regards, >> John >> >> > If I C-c C-c in the following code: >> > >> > #+BEGIN_SRC python :session transect >> > import numpy as np >> > x = np.arange(12) >> > #+END_SRC >> > >> > Emacs hangs the first time with minibuffer message of "Sent >> > python-eldoc-setup-code". If I C-g, I can edit the org buffer again. All >> > other invocations of that code and the minibuffer message is "executing >> > Python code block...", but still emacs hangs until I C-g. >> > >> > If I look at the *transect* buffer, I see the following. The code runs >> just >> > fine, but for some reason it does not return. >> > >> > -k. >> > >> > >> > >> > Enthought Canopy Python 2.7.3 | 64-bit | (default, Dec 2 2013, 16:19:29) >> > [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin >> > Type "help", "copyright", "credits" or "license" for more information. >> > import numpy as np >> > Start .pythonrc >> > End .pythonrc >> >>>> >> >>>> import numpy as np >> > >> > x = np.arange(12) >> > x = np.arange(12) >> > >> > >> > >> open('/var/folders/60/jb7kfrsn2jd90hpcgj4m_wrc0000gn/T/babel-28022EFF/python-28022Yjm', >> > 'w').write(str(_)) >> > >> open('/var/folders/60/jb7kfrsn2jd90hpcgj4m_wrc0000gn/T/babel-28022EFF/python-28022Yjm', >> > 'w').write(str(_)) >> > >> > >> > >> > >> > 'org_babel_python_eoe' >> > 'org_babel_python_eoe' >> >>>> >> >>>> >>> >>> >>> >>> >>> Traceback (most recent call last): >> > >> > File "<stdin>", line 1, in <module> >> > NameError: name '_' is not defined >> >>>> >> >>>> >>> >>> 'org_babel_python_eoe' >> >>>> import numpy as np >> > >> > import numpy as np >> > x = np.arange(12) >> >>>> >> >>>> x = np.arange(12) >> > >> > >> >>>> >> > >> open('/var/folders/60/jb7kfrsn2jd90hpcgj4m_wrc0000gn/T/babel-28022EFF/python-28022lts', >> > 'w').write(str(_)) >> >>>> >> >>>> >> > >> open('/var/folders/60/jb7kfrsn2jd90hpcgj4m_wrc0000gn/T/babel-28022EFF/python-28022lts', >> > 'w').write(str(_)) >> > >> >>>> >> > >> >>>> >> > 'org_babel_python_eoe' >> >>>> >> >>>> 'org_babel_python_eoe' >> > >> > 'org_babel_python_eoe' >> >>>> >> >>>> >> > >> > >> > >> > >> -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D