doomemacs / doomemacs/core

Jupyter fails to function after upgrade

Open
#7,354 7 comments 4 reactions 0 assignees View on GitHub
is:bug needs-triage
Dominant language
Emacs Lisp
Stars
22.7k
Forks
3.1k
Avg merge
10h 46m
Merged PRs (30d)
4

Description

### I confirm that...

- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.

- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.

- [X] The issue can be reproduced on the **latest** available commit of Doom.

- [X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. *(Doom does not support development builds like 29+ or any version ending in .50 or .9x)*

### Expected behavior

When I have `emacs-jupyer` loaded with `(org ... +jupyter ...)` in `init.el`, the `jupyter-python` environment should be available in Babel

### Current behavior

When I attempt to execute a `jupyter-python` block in an org file, I get the following error message:
```
org-babel-execute-src-block: No org-babel-execute function for jupyter-python!
```
The most recent messages are as follows:
```
Company: An error occurred in auto-begin
Company: backend company-capf error "Invalid search bound (wrong side of point)" with args (prefix)
Company: An error occurred in auto-begin
Company: backend company-capf error "Wrong type argument: integer-or-marker-p, nil" with args (prefix)
Company: An error occurred in auto-begin
Company: backend company-capf error "Wrong type argument: integer-or-marker-p, nil" with args (prefix)
Company: An error occurred in auto-begin
Company: backend company-capf error "Wrong type argument: integer-or-marker-p, nil" with args (prefix)
Quit [3 times]
mouse-minibuffer-check: Minibuffer window is not active
Quit
org-babel-execute-src-block: No org-babel-execute function for jupyter-python!
Your doom-info was copied to the clipboard.
```

I created [this issue](https://github.com/emacs-jupyter/jupyter/issues/489) in the emacs-jupyter repo, which linked to (this issue)[https://github.com/org-roam/org-roam/issues/2361] in the org-roam repo, which led me to try the solution from [this comment on it](https://github.com/org-roam/org-roam/issues/2361#issuecomment-1680562960), which didn't work. Looking at emacs-jupyter, it seems that the canonical way to activate it is with
```
(org-babel-do-load-languages
'org-babel-load-languages
'((emacs-lisp . t)
(julia . t)
(python . t)
(jupyter . t)))
```
and the `'org-babel-load-languages` that I see upon inspection has `jupyter-python` in it instead, but I'm unsure if that's a problem in any way. I also see other `jupyter` functions working in emacs, just not this one, so the module is loading correctly. I have attempted adding the `do-load-langauges` hook myself in `config.el` but this too has failed to resolve the issue.

### Steps to reproduce

1. Open an org file
2. Create a block with the header `#+begin_src jupyter-python :session whatever`
3. Execute with `C-c C-c`

### System Information

https://pastebin.com/JNM6Vfct

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.