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
I'm following this pattern and getting occasional segfaults when I try to access the imported module (the one that I pycopy!ed). Do I need to do something like GC protect that pointer so it doesn't get GCed? Can I even do that on the julia side or do I need to do it on the python side somehow?
Wow and when I pyimport the module afresh each time before referring to it. I suspect this may be something specific to my module and how I'm using it!
Activity
cjdoris commentedon Nov 17, 2021
Glad you like it!
The equivalent in PythonCall is:
boriskaus commentedon Nov 17, 2021
Thanks, that works! See https://github.com/JuliaGeodynamics/geomIO. Next up is figuring out why CI fails on windows, but works on Mac/Linux.
kleinschmidt commentedon Aug 15, 2024
I'm following this pattern and getting occasional segfaults when I try to access the imported module (the one that I
pycopy!ed). Do I need to do something like GC protect that pointer so it doesn't get GCed? Can I even do that on the julia side or do I need to do it on the python side somehow?kleinschmidt commentedon Aug 15, 2024
I get the same behavior FWIW when using
Ref{Py}to store the imported module as well...kleinschmidt commentedon Aug 16, 2024
Wow and when I
pyimportthe module afresh each time before referring to it. I suspect this may be something specific to my module and how I'm using it!