Skip to content

Comments

Support user_expressions in kernel execute requests#253

Open
juntyr wants to merge 6 commits intojupyterlite:mainfrom
juntyr:patch-1
Open

Support user_expressions in kernel execute requests#253
juntyr wants to merge 6 commits intojupyterlite:mainfrom
juntyr:patch-1

Conversation

@juntyr
Copy link
Contributor

@juntyr juntyr commented Jan 18, 2026

Fixes #251

@github-actions
Copy link
Contributor

lite-badge 👈 Try it on ReadTheDocs

@jtpio jtpio added the enhancement New feature or request label Jan 20, 2026
@jtpio jtpio added this to the 0.8.0 milestone Jan 20, 2026
@juntyr
Copy link
Contributor Author

juntyr commented Jan 21, 2026

Thanks for taking a look @jtpio! What's the current (rough) timeline for v0.8.0?

@jtpio
Copy link
Member

jtpio commented Jan 30, 2026

Thanks @juntyr!

Just tried locally with the built wheel for this PR and jupyterlab-myst. It seems like it requires the markdown cell to be run twice for the expression to be evaluated and rendered correctly?

jupyterlite-pyodide-kernel-user-expressions.mp4

@juntyr
Copy link
Contributor Author

juntyr commented Jan 30, 2026

@jtpio Huh. I developed this by putting breakpoints into the relevant myst and kernel code, and with that, everything worked correctly, updating immediately. So I wonder if me using breakpoints messed with some timings to allow the updates to go through the first time.

What does your dev console say when you first execute the cell? Mine is always full of myst debug logs

@jtpio
Copy link
Member

jtpio commented Jan 30, 2026

Actually this may be a more general issue with JupyterLab or jupyterlab-myst, as this also happens with jupyterlab==4.5.3 and jupyterlab-myst==2.6.0:

jupyterlab-myst-eval.mp4

@juntyr
Copy link
Contributor Author

juntyr commented Jan 30, 2026

@jtpio That could be it! I was testing with jupyterlab~=4.5.0 (likely 4.5.2 when I created this PR) and jupyterlab-myst~=2.6.0 (2.6.0)

@juntyr
Copy link
Contributor Author

juntyr commented Feb 10, 2026

@jtpio Is there anything still needed for this PR?

@jtpio
Copy link
Member

jtpio commented Feb 10, 2026

The PR itself looks good.

The remaining question was more to know where the issue mentioned above belongs. I see you opened jupyter-book/jupyterlab-myst#289 so maybe we can just move forward with this and keep an eye on jupyter-book/jupyterlab-myst#289.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jupyterlab-myst fails to eval

2 participants