-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot import name '_core' #423
Comments
I also encounter this problem in my Ubuntu 18.04 system. |
Same: File "/root/miniconda3/envs/chrono/lib/python3.10/site-packages/pychrono/init.py", line 54, in Did the conda install with the latest release here: Btw, this is on python 3.10 |
I also encounter this issue on windows with python 3.9 & both pychrono v7 and 8. Any solution would be greatly appreciated! |
Same here, Ubuntu 20.04, building from source. I've tried on a venv of 3.10 and 3.11, on the OS installation of 3.8. All receive the same error as CosteaPaul. |
Unfortunately we have seen many users affected by this issue (during hands-on sessions it was really a nightmare!) but so far we failed in spotting the cause: apparently some users were affected while others did not. And this was independent from the OS, the Python or the PyChrono version. While we investigate the issue we suggest those keenest users to build PyChrono by their own from C++ source (section B here). |
Thanks Riccardo, it would be great if also other users can confirm that the fix applies also to them! |
I have a similar issue. This is on Fedora37 using chrono I've built from source.
|
I've got it working by setting: I installed it to |
"ImportError: cannot import name '_core' from partially initialized module 'pychrono' (most likely due to a circular import)" |
Talking about linux systems:
Not so shure about windows system. |
Hello, I did fresh installation on my Windows and I've encountered with the running issue.
My script failed on the line import pychrono as chrono where after run under the spyder I've got this error message
The text was updated successfully, but these errors were encountered: