Error after installing python bindings

[MissingSignal]

Dear mantainers,

When compiling the Superbuild with ROBOTOLOGY_USES_PYTHON=ON I get two folders in robotology-superbuild/build/install/lib/ :

Python3
└── dist-packages
    ├── yarp-3.10.1.dist-info
    │   ├── INSTALLER
    │   └── METADATA
    ├── yarp.py
    └── _yarp.so

Python3.12
└── dist-packages
    ├── icub_models
    │   ├── icub_models.py
    │   └── __init__.py
    ├── icub_models-3.0.0.dist-info
    │   ├── INSTALLER
    │   └── METADATA
    ├── icub.py
    └── _icub_python.so

When I ask Python to import yarp I get No module named 'yarp'

---

A dirty workaround is to simply copy the content of /Python3 folder into /Python3.12 but ...
What is the best way to handle this problem ?

Many thanks in advance !

[traversaro]

Thanks @MissingSignal for reporting the problem!

Can you please specify:

• Which Linux distribution are you using?
• How did you installed the robotology-superbuild dependencies (i.e. apt or conda).
• Did you run the installation in a virtual environments? Did you installed any package via pip ?

To quickly report on the installed software, you can also run curl -fsSL https://raw.githubusercontent.com/ami-iit/log-installed-software/main/src/log.py | python and report the generated installed_software.txt file.

[traversaro]

Also, can you report the content of robotology-superbuild/build/install/share/robotology-superbuild/setup.sh ?

[MissingSignal]

Sorry @traversaro for the missing details:

• I'm using a fresh installation of Ubuntu 24.04
• I opted for the installation from source using apt
• The installation is "system-wise" using the default python 3.12 bundled with ubuntu 24.04

here the generated setup.sh

export ROBOTOLOGY_SUPERBUILD_SOURCE_DIR=/usr/local/src/robot/robotology-superbuild
export ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX=/usr/local/src/robot/robotology-superbuild/build/install

export PATH=$PATH:$ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX/bin


export YARP_DATA_DIRS=${YARP_DATA_DIRS:+${YARP_DATA_DIRS}:}$ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX/share/yarp:$ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX/share/iCub:$ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX/share/ICUBcontrib:$ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX/share/ergoCub

export CMAKE_PREFIX_PATH=${CMAKE_PREFIX_PATH:+${CMAKE_PREFIX_PATH}:}${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+${LD_LIBRARY_PATH}:}${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/lib
export BLOCKFACTORY_PLUGIN_PATH=${BLOCKFACTORY_PLUGIN_PATH:+${BLOCKFACTORY_PLUGIN_PATH}:}$ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX/lib/blockfactory
export XDG_DATA_DIRS=${XDG_DATA_DIRS:-"/usr/local/share:/usr/share"}:$ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX/share


export GZ_SIM_SYSTEM_PLUGIN_PATH=${GZ_SIM_SYSTEM_PLUGIN_PATH:+${GZ_SIM_SYSTEM_PLUGIN_PATH}:}${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/lib
export GZ_SIM_RESOURCE_PATH=${GZ_SIM_RESOURCE_PATH:+${GZ_SIM_RESOURCE_PATH}:}${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share/gazebo/models:${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share/iCub/robots:${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share:${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share/ergoCub/robots:${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share/gazebo/worlds

export ROS_PACKAGE_PATH=${ROS_PACKAGE_PATH:+${ROS_PACKAGE_PATH}:}${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share
export AMENT_PREFIX_PATH=${AMENT_PREFIX_PATH:+${AMENT_PREFIX_PATH}:}${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}
export GAZEBO_MODEL_PATH=${GAZEBO_MODEL_PATH:+${GAZEBO_MODEL_PATH}:}${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share/gazebo/models:${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share/iCub/robots:${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share:${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/share/ergoCub/robots

export PYTHONPATH=${PYTHONPATH:+${PYTHONPATH}:}${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/lib/python3.12/dist-packages
export PATH=$PATH:${ROBOTOLOGY_SUPERBUILD_INSTALL_PREFIX}/lib/python3.12/dist-packages/bin

[traversaro]

Thanks for the issue! There were two problems in the current code, both fixed in #1763 . Once #1763 is merged, you can update the superbuild and everything should work fine.

[traversaro]

I will also cherry-pick the fix on the releases/2024.11 branch, so it is ready for a possible future 2024.11.2 release.

[traversaro]

@MissingSignal the problem should have been fixed by #1763, feel free to comment if you still have the problem.

[MissingSignal]

@traversaro I confirm #1763 fixed the problem.
Thank you for the lightning-fast support 🙏🏻