From: "Barton, Mark" <Mark.Barton@disney.com>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: "50514@debbugs.gnu.org" <50514@debbugs.gnu.org>,
Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#50514: 28.0.50; org inline call to python src block req C-g to break
Date: Tue, 14 Sep 2021 19:25:46 +0000 [thread overview]
Message-ID: <073CC0D1-9900-4613-87E8-D69EA1C11623@disney.com> (raw)
In-Reply-To: <87sfy7qadr.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On Sep 14, 2021, at 11:29 AM, Augusto Stoffel <arstoffel@gmail.com<mailto:arstoffel@gmail.com>> wrote:
Hi Mark,
thanks for testing.
What happens if you start Emacs, then do 'M-x run-python', then 'M-x
rename-buffer' to rename the Python shell as '*python-chain*', and then
execute your notebook as usual?
If this works, then the problem is in how ob-python initializes the
shell. The Python shell needs a fraction of a second to start up, and
if you send stuff to it before it's ready, it can be cause problems.
Augusto,
It runs as expected if I do that.
As a summary of what I have tried that works is:
- If I create the python buffer with this evaluation before running the org file/notebook.
(python-shell-make-comint "python" "python-chain" nil)
- If I don’t use the session header property to enable multiple src blocks to share the python session.
- If I revert back to the python.el on August 27th.
Possibly the older python.el was slow enough where I did not experience this problem.
Thanks for introducing me to the trace-function. I will try that with the org babel functions to see if I can learn something more about the initialization process.
[-- Attachment #2: Type: text/html, Size: 2354 bytes --]
next prev parent reply other threads:[~2021-09-14 19:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 23:06 bug#50514: 28.0.50; org inline call to python src block req C-g to break Barton, Mark
2021-09-11 13:04 ` Lars Ingebrigtsen
2021-09-11 13:26 ` Augusto Stoffel
2021-09-12 6:22 ` Barton, Mark
2021-09-12 6:51 ` Augusto Stoffel
2021-09-12 8:27 ` Barton, Mark
2021-09-12 9:15 ` Augusto Stoffel
2021-09-12 17:00 ` Barton, Mark
2021-09-12 20:04 ` Barton, Mark
2021-09-14 6:42 ` Augusto Stoffel
2021-09-14 17:54 ` Barton, Mark
2021-09-14 18:29 ` Augusto Stoffel
2021-09-14 19:25 ` Barton, Mark [this message]
2021-09-14 19:31 ` Augusto Stoffel
2021-09-14 22:20 ` Barton, Mark
2021-09-15 6:28 ` Augusto Stoffel
2021-09-14 19:36 ` Augusto Stoffel
2021-09-15 8:02 ` Lars Ingebrigtsen
2022-08-25 15:12 ` Lars Ingebrigtsen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=073CC0D1-9900-4613-87E8-D69EA1C11623@disney.com \
--to=mark.barton@disney.com \
--cc=50514@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=larsi@gnus.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.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).