This not exactly a duplication of bug:1130354 but it is most probably caused by the same issue. Hierarchical information is not propagated to Python wrapped entities returned by member functions of Hierarchical<Foo>.
Hierarchical<Foo> being a base class of Foo makes thing more difficult. It might look nice in C++ implementation but adding Python specializations makes it a pain to work with. Even if the bug resides in the Python wrapper I will not spend more time at it unless we have a general discussion of how to fix generation of Python specializations of C++ objects returned from
Foo Hierarchical<Foo>::bar();
methods, where Hierarchical<Foo> information is also propagated to the returned object.
This not exactly a duplication of bug:1130354 but it is most probably caused by the same issue. Hierarchical information is not propagated to Python wrapped entities returned by member functions of Hierarchical<Foo>.
Hierarchical<Foo> being a base class of Foo makes thing more difficult. It might look nice in C++ implementation but adding Python specializations makes it a pain to work with. Even if the bug resides in the Python wrapper I will not spend more time at it unless we have a general discussion of how to fix generation of Python specializations of C++ objects returned from
Foo Hierarchical< Foo>::bar( );
methods, where Hierarchical<Foo> information is also propagated to the returned object.