Martijn Visser

Thanks for trying and including versioninfo. I noticed you run with 1 interactive thread and I with 0. If I add an interactive thread, the segfault goes away. This may...

Yeah that seems to be spot on. Ran it with c934d808e1ecb37d9c3d11f50b9939c4d8e9d32a: Works with 1 interactive thread when both run on the same inteactive thread: ``` julia> using PythonCall ┌ Info:...

Calling `propertynames(x`) doesn't segfault, but via REPLCompletions it does. See the full stacktrace for the REPLCompletions path: https://github.com/JuliaPy/PythonCall.jl/issues/586#issuecomment-2799027653 I don't know much about the REPL or how thread safety is...

After reading https://github.com/JuliaPy/PythonCall.jl/pull/635#issuecomment-3042334536 I looked a bit more into the GIL with [these Python docs](https://docs.python.org/3/c-api/init.html#non-python-created-threads). The tab completion works if I we can acquire the GIL in the non-main Julia...

Hi, yeah I just wanted to echo @evetion's remarks, happy to see this package has been useful for you. I'm currently not actively using this package, hence the inactivity here....

I don't think a specific function for this property is sufficiently generic. Not sure where this is information is stored, but you can try the `getfield(feature::AbstractFeature, name::Union{AbstractString,Symbol})` method with `name...

Fixed by #473.

This should be possible, we already do some logging on a crash: https://github.com/Deltares/Wflow.jl/blob/37ae6ddf1d61aa1d3e0b99581bb94a14b53cc274/src/Wflow.jl#L169-L178 That could be expanded to write the state as well.

Don't remember the reasons, but this was also discussed in https://github.com/yeesian/ArchGDAL.jl/pull/327#issuecomment-1259493599, and perhaps the macroexpand linked there can help?

I guess this is not an issue anymore since the downstream packages have adapted. I just fixed part of that in vscode-julia, https://github.com/julia-vscode/julia-vscode/pull/3541.