"Achim Domma" <achim.domma@syynx.de> writes:

Hi,

I'm exposing a lot of classes called DrawableXXX and PathXXX. I want to put them in two sub-modules Drawable and Path, so that the python classes would be called Drawable.XXX and Path.XXX. As far as I understand the documentation of scope, I have to do something like this:

BOOST_PYTHON_MODULE(myModule) { // register classes which are not part // of Drawable and Path // ...

registerDrawableClasses(); registerPathClasses(); }

void registerDrawableClasses() { scope drawable = ???; class_<DrawableXXX>("XXX") .def(... }

void registerPathClasses() { scope path = ???; class_<PathXXX>("XXX") .def(... }

In the documentation nested classes are used, so should I use an empty class like this?

struct drawable_place_holder {}; scope drawable = class_<drawable_place_holder>("Drawable",no_init);

Is that the way to go?

No, just use the Python/'C' API to create a new module object, grab it with a handle<>. Something like: handle<> inner_module(PyModule_New("myModule.Drawable")); scope drawable = object(inner_module); ...but look in the Python docs for the right way to use the module creation functions. Don't expect the above to work verbatim. -- David Abrahams dave@boost-consulting.com * http://www.boost-consulting.com