Christopher Rowley
Christopher Rowley
Thank you for looking into this. I had no idea there was such a thing as a benign segfault! Given it is so important for Julia's GC I guess we...
I think this was largely fixed (well, worked-around) by setting the env var `PYTHON_JULIACALL_HANDLE_SIGNALS=yes`? This installs the Julia signal handler, so that GC works as expected. The downside is that...
The reason why `PYTHON_JULIACALL_HANDLE_SIGNALS=no` is the default is because setting it to `yes` messes with ordinary Python behaviour. For example, Ctrl-C no longer raises a KeyboardInterrupt but just crashes Python...
The issue over on Julia: https://github.com/JuliaLang/julia/issues/53363
OK, as far as I can tell (based on comments by @topolarity) the issue occurs when Python was not built with the `--enable-shared` flag (which in particular enables `-fPIC`). The...
https://github.com/conda-forge/python-feedstock/issues/222 Looks like pyjulia already experienced some issues with statically linked Python.
There's a new version of juliacall out which requires julia
I confirmed that JuliaCall works with 1.10.3 so I have made a release (JuliaCall 0.9.20) with the updated julia compat entries.
Unfortunately this isn't possible. `help(x)` gets the docstring from `type(x).__doc__`, and since all Julia objects are wrapped with the same Python type, they all must have the same docstring. However...
No that looks like a bug. Will take a look.