separate the ROS part and the python part. plugins ?

[asmodehn]

This is important to do as early as possible to ease maintenance. It will also make the job of managing package dependencies much easier.

Pyros should be python only (with its python dependencies) It can have a rosinterface 'plugin' that depends on ROS (for which ROS dependencies are enforced for different distros) It can have other plugins for other multiprocess frameworks.

It means we need first implement plugin and extensions and make sure they work fine in ROS ecosystem.

We could use twisted plugin system : https://github.com/twisted/twisted/blob/trunk/src/twisted/plugin.py Or reuse some others :

• https://github.com/mitsuhiko/pluginbase
• http://wehart.blogspot.kr/2009/01/python-plugin-frameworks.html

It seems there is no standard way...

[asmodehn]

Currently separating the "interfaces" in separate packages.

This should allow for :

• simpler launch usecase for ROS
• clean namespace packages for later, if ever.
• pure python version when possible
• package finding each other to be used as extensions (a setuptools/pkg_resources based solution for plugins)

[asmodehn]

ROS intrface has been separated. closing this.