[C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject (original) (raw)
Shin-ichi MORITA shin1_morita at yahoo.co.jp
Mon Dec 12 16:55:46 CET 2005
- Previous message: [C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject
- Next message: [C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Roman Yakovenko <roman.yakovenko at gmail.com> wrote:
You are missing init method. It is a must to call module1.Derived.init( self )
I think that init() is implicitly called because init() is not overriden.
In case that there is only one single module, everything is ok.
My case has two modules: One exposes a function which signature contains a base class, the other exposes a derived class.
Thanks.
STOP HIV/AIDS. Yahoo! JAPAN Redribbon Campaign 2005 http://pr.mail.yahoo.co.jp/redribbon/
- Previous message: [C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject
- Next message: [C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]