You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
using PythonCall in Pluto crashes Pluto Malt.TerminatedWorkerException #711
Describe the bug
I would like to experiment with PythonCall in Pluto. In a new installation of Pluto v0.20.20 the single line using PythonCall crashes the new notebook with a Malt.TerminatedWorkerException. Importing other packages like PlutoPlotly works just fine.
Your system
Please provide detailed information about your system:
tested on ubuntu WSL on Windows and on NixOS
Julia 1.12.1 and Pluto 0.20.20
Additional context
I think this was once working if I remember right. Unfortunately I cannot extract anymore detailed error notice. When switching to using Distributed instead of Malt Pluto.run(workspace_use_distributed_stdlib=true), I get a EOFError
Worker 2 terminated.Distributed
.ProcessExitedExceptionUnhandled Task ERROR: EOFError: read end of file
I think you'll need to dig into what error is actually happening on the worker process - can you get the underlying exception or stack trace or anything?
One thought is that there are known issues with Python 3.14 that can cause unexpected exits. If you pin to Python 3.13 does the issue persist?
Edit: okay, I now noticed the new release & the FAQ with python 3.14. This can be closed
sorry missed this post.
I now tested this in an explicit Malt process. (From Pluto.jl I do not get any feedback in the console). "Unfortunately", in the manual Malt-Worker session, it works. I used this command: Malt.remote_eval_fetch(worker, :(using Pkg;Pkg.activate(mktempdir()); ENV["JULIA_CONDAPKG_BACKEND"] ="MicroMamba";Pkg.add("PythonCall");using PythonCall))
in the Malt worker it actually installed python 3.13, I assume Pluto does something similar but cannot confirm right now
Activity
behinger commentedon Nov 13, 2025
running into the same bug :(
I can add that in Julia 1.11.5 it still works (I have to use MicroMamba backend though, pixi runs into a infinite loop)
cjdoris commentedon Nov 14, 2025
I think you'll need to dig into what error is actually happening on the worker process - can you get the underlying exception or stack trace or anything?
One thought is that there are known issues with Python 3.14 that can cause unexpected exits. If you pin to Python 3.13 does the issue persist?
behinger commentedon Nov 27, 2025
Edit: okay, I now noticed the new release & the FAQ with python 3.14. This can be closed
sorry missed this post.
Malt.remote_eval_fetch(worker, :(using Pkg;Pkg.activate(mktempdir()); ENV["JULIA_CONDAPKG_BACKEND"] ="MicroMamba";Pkg.add("PythonCall");using PythonCall))