Open MilesCranmer opened 9 months ago
Yeah we should at least check for this and issue a better error message (like we do in PythonCall).
Maybe we could do it similarly to how PyTorch is handled
But not sure if it needs to also be checked on the PythonCall.jl/PyCall.jl side?
I would not expect this to work anyways but just wanted to point it out:
This will not be an issue if everyone moves to
juliacall
, but the transition period where some packages use PyCall (like PyPlot) and some packages use PythonCall may cause some of these issues.Maybe there is a safety switch to get around this issue temporarily.