Open JianghuiDu opened 4 months ago
This seems to only happen to Julia 1.10, but not 1.9.
Hmm, there are a lot of moving parts.
First, I'd try to see if SymPyPythonCall
works.
That should be a drop-in replacement and might just be the solution.
Otherwise, is the code in a package? If so, I could run downstream tests with it so we can see a grid of OS and julia versions.
I have move my development to WSL+Docker and there is no problem there with the new SymPy version, but on Windows itself this problem persists and SymPyPythonCall
is even worse as it kills my computer instantly. Very strange...
Yes, very strange. I don't know if you have code to share that I can look at. Maybe there is something I can spot.
My package was build using v1.0 but after updating to v2.0 the same code has becoming extremely slow and causing memory errors. I have a
for
loop with 14 iterations where I do symbolic calculations. After updating to v2, Julia exists abruptly after a few iterations, even though I tested that I can manually run each iteration individually. It would appear thatSymPy.solveset
in the new version cannot handle large equations like the old one. I'm not even sure what the problem is because the loop constantly causes Julia breakdown.These are some of the errors I got:
or