Geoffrey M. Furnish wrote: <explanation of state of work of C++ SIG> As i'm new too, this helped me a lot, thanks, Geoffrey. I'd like to suggest to send this text to every new subscriber so they'll get an idea immediately (i subscribed to a genetic programming list and they have a very good text they send to every new subscriber, i found this very helpful.) But i have one further question: To have python shadow classes that wrap C++ classes, one can use SWIG. Doesn't it make more sense to extend the SWIG shadow class concept or its C++ parsing capabilities (if necessary) than writing your PyObject-derived C++ classes? I don't see the advantage. In Python, you do not need to model a class hierarchy of wrapper classes to resemble the inheritance of the wrapped C++ classes. Every wrapper class can be solo. Excuse me if this sounds blasphemic, i just wanna know what's the advantage of the C++ binding compared to SWIGging, practically? Dirk Heise, Braunschweig, Germany dheise@metronet.de _______________ C++-SIG - SIG for Development of a C++ Binding to Python send messages to: c++-sig@python.org administrivia to: c++-sig-request@python.org _______________