-
Notifications
You must be signed in to change notification settings - Fork 194
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
Error: Module not found YARP when i try to use it using python 3.11 #3110
Comments
If you type |
i did what you told you can see step i follow maybe i did something wrong Error log:
|
Thanks, can you report the content of
Are you sure that you enabled the |
content of pyhtonpath:
Yes i enable this |
Can you check the content of |
there no folder in lib named as python3.11. |
Interesting, can you report the |
Those files you asked for were too large, so I attached them:
|
Did you enable the ROBOTOLOGY_USES_PYTHON superbuild CMake option? |
That is quite strange, in YARP's |
@traversaro After run Output:
|
@traversaro i think you forgot to reply?? |
Sorry, I asked to run |
sorry for late response, Build target YARP 100% |
Ok, can you please report the |
|
You need to run |
With sourcing nothing happen it just go to next line Without sourcing it show error:
|
If you do not get any error, it means that yarp is found correctly. I am not sure how to make Spyder use superbuild's yarp. |
Looking on Google, you could:
|
I will describe what i did from start:
1. I did source install in robsub envoirment unsing Conda forge. steps i follow (https://github.com/robotology/robotology-superbuild/blob/master/doc/conda-forge.md#binary-installation)
2. Then i install this example in same robsub (https://icub-tech-iit.github.io/documentation/sw_installation/check_your_installation/#check-icub) i run on gazebo.
3. Then in last i install python 3.11.7 and using spyder 5.5.4 in robsub and try to run this code https://robotology.github.io/robotology-documentation/doc/html/icub_python_basic_motor.html
ERROR LOG:
The text was updated successfully, but these errors were encountered: