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
Describe the bug
PyJulia only runs correctly out of the box on Linux systems when the installed Python is built with --enable-shared. However, installing Python in a conda environment on Linux yields a statically linked Python that PyJulia doesn't support.
Python Environment (please complete the following information):
Environment (e.g., conda): conda inside a Docker container with Ubuntu 16.04 base image
I don't think there should be a large performance penalty since the GAlibrate functions in Julia need to be JIT compiled anyways when first called. Although I guess it could add some latency to PyCall.
The run_gao_julia.py module could be patched to check the OS (using sys.platform) and for linux it can apply the above Turn off compilation cache workaround. Something like:
Describe the bug
PyJulia only runs correctly out of the box on Linux systems when the installed Python is built with
--enable-shared
. However, installing Python in a conda environment on Linux yields a statically linked Python that PyJulia doesn't support.Python Environment (please complete the following information):
Additional context
The troubleshooting guide in the PyJulia docs, https://pyjulia.readthedocs.io/en/latest/troubleshooting.html#your-python-interpreter-is-statically-linked-to-libpython, includes several workarounds.
Potential Fix
I think for GAlibrate, the Turn off compilation cache workaround probably makes the most sense:
I don't think there should be a large performance penalty since the GAlibrate functions in Julia need to be JIT compiled anyways when first called. Although I guess it could add some latency to PyCall.
The
run_gao_julia.py
module could be patched to check the OS (usingsys.platform
) and for linux it can apply the above Turn off compilation cache workaround. Something like:The text was updated successfully, but these errors were encountered: