Hi Daniel, there wasn't any breaking changes to "Shiboken::Converter<T>::toPython(...)", at least as far as I know it, the other folks here could have changed something when I was not looking. And I wouldn't notice because we normally perform those to Python conversions automatically or in custom code inserted via the type system XML file. That way instead of calling "toPython" directly, the " generator macro "%CONVERTTOPYTHON[YourTypeHere](arg0, arg1)" is called instead.
It is better described here: http://www.pyside.org/docs/shiboken/typesystemvariables.html#example I'm wondering if you're writing your binding with your bare hands, and just calling libshiboken here and there. That can be very problematic, because there is a good deal of tasks (like initialize the module and it's dependencies) that the generator already does for you and are not explicitly documented. The idea is to describe your bindings via the type system XML and let the generation process happen. If you're wrapping a library that will work on it's own, you can check these tutorials: http://developer.qt.nokia.com/wiki/PySide_Binding_Generation_Tutorial http://www.setantas.net/blog/2011/03/08/python-bindings-for-libepub-using-shiboken/ On the other hand, if you're trying to embed your binding in a C++ program check this out: http://lynxline.com/superhybrids-part-2-now-qt-pyside/ I hope that helps. Cheers, Marcelo _______________________________________________ PySide mailing list PySide@lists.pyside.org http://lists.pyside.org/listinfo/pyside
