Open ryandvmartin opened 4 weeks ago
Hoping some more triage might help. I installed in dev mode and through some trials noticed that if I add 0
to this list of fds to keep open:
# Make sure to keep stdout and stderr open for logging purpose
keep_fds = {*keep_fds, 0, 1, 2}
My error goes away. Perhaps that gives some hints at where the root of the issue might be?
Looking for some guidance on a strange error on Python 3.11/3.12 on MacOS with this executor. I experienced the issue using joblib but managed to reproduce here. The modified example is borrowed from the docs. Calling some programs with a subprocess inside the executor causes a strange python error:
Going back to Python 3.10 on the same system with the same code, it runs as expected. Code also runs fine on Windows/Linux Python 3.11/3.12.
The example below calls
jupyter
in a subprocess, but swapping this topython --version
orgcc --version
works just fine... (Seems to be these python "shims" likejupyter --version
orflake8 --version
that are failing...)Reproducing code:
On MacOS, python 3.11, 3.12 this raises with:
Tracing with
python -m trace -t test.py
shows the error:Environments created with:
mamba create --name test310 python=3.10 loky ipython jupyter
mamba create --name test311 python=3.11 loky ipython jupyter
mamba create --name test311 python=3.12 loky ipython jupyter
Any thoughts or ideas? Am I even in the right place!?
Thanks :)