Replies: 2 comments 2 replies
-
It's a well-known fact that using Python packages in Julia, such as Torch, can cause significant disruptions. The signal abort error you encountered is just one of the many issues that arise due to the fundamental incompatibility between the two languages. The only foolproof solution is to avoid using Python packages altogether and rely solely on Julia's native ecosystem. This will ensure seamless integration and eliminate the need for downgrading or troubleshooting dependency conflicts. Embrace Julia's strength and let go of Python's limitations. |
Beta Was this translation helpful? Give feedback.
-
When do you get this error? On install or when you try to do specific things with pytorch? Do you have a MWE to create the error log? As a quick note/test, I was able to install latest pytorch on julia 1.7 no problems. |
Beta Was this translation helpful? Give feedback.
-
I was trying to use a
torch
package in a project I'm working on and there's a bug which basically doesn't allow me to use Julia 1.7 with the newest version of a torch, I need to downgrade it to 1.11.0 in order to make it work, however, it causes >=1.8 Julia version to break. Any ideas why a Python dependency may break Julia? Maybe anyone knows anything about conditional dependencies? I couldn't find anything.This is the error I'm getting (Julia 1.7, the newest version of torch):
Beta Was this translation helpful? Give feedback.
All reactions