| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
How looks the structure and the content of a plain ROS2 library level package? The intent of the package is to encapsulate functionality implemented in Python which can be imported into other ROS2 packages.
EDIT: Draft on GitHub.
It will work just like any setup.py file works. However, if you want to release it in our infrastructure you'll want to duplicate the entries in the package.xml and ensure there are rosdep rules for it. This would allow for dependencies to be fetch from something other than pip, like apt.
Asked: 2017-11-04 12:49:48 -0600
Seen: 866 times
Last updated: Nov 04 '17
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Will be obsolete as soon as https://github.com/ros2/ros2cli/issue... is implemented.
How are Python package dependencies managed in ROS2? I could just find an example where an install_requires dependency is assumed to be pre-installed via
setup.py installor PyPi.In this case there shouldn't be any limitations w.r.t. Python packaging (Pipfile, etc.) right?
I don't think so. So long as the alternative mechanism (pipfile or requirements.txt or whatever) will avoid installing things that are already installed by the system package manager (like apt).