Python classes with multiple bases are convertible only to the first class in the lists (even if super(classname, self).__init__() is called)

[Piotr Jaroszyński <p.jaroszynski@…>]

first reported here: ​http://mail.python.org/pipermail/c++-sig/2007-October/012926.html

C++:
#include <boost/python.hpp>

namespace bp = boost::python;

struct A { };
struct B { };

void test_A(const A &) { }
void test_B(const B &) { }

BOOST_PYTHON_MODULE(multiple_inheritance)
{
    bp::def("test_A", &test_A);
    bp::def("test_B", &test_B);

    bp::class_<A>("A", bp::init<>());
    bp::class_<B>("B", bp::init<>());
}

Python:
class C(A, B):
    pass

test_A(C())
test_B(C())

And I get:
Traceback (most recent call last):
  File "./multiple_inheritance.py", line 10, in <module>
    test_B(C())
Boost.Python.ArgumentError: Python argument types in
    multiple_inheritance.test_B(C)
did not match C++ signature:
    test_B(B)

I will try to figure it out once I am done with the exceptions.

[Piotr Jaroszyński <p.jaroszynski@…>]

bleh, I wanted to choose the Python component.

[troy d. straszheim]

You have to initialize your base classes in the derived object's constructor. I committed a passing test to git, will work its way into svn eventually:

​http://gitorious.org/~straszheim/boost/straszheim/commit/ec9c7f7b48a40bf8136597242457f40a349b2fe3

[AnyOldName3]

I made a detailed comment explaining why I think this issue should be reexamined, but the spam filter ate it. Hopefully, an admin can approve it.