If you are interested in more than just using the PySide bindings then your wanting probably falls in one of these categories:

Create your own bindings for Qt based libraries

If you have a library built on top of Qt and want to make it available on Python, then check out the Binding Generator section on how to write type system files to export it, generate the source code and build. Keep in mind that this new binding will depend on PySide as much as on Qt.

Create your own bindings for non-Qt based libraries

The process should be just the same as with the Qt based libraries, except that, for our shame, we’re still too tied to Qt and our generator is not the best choice to create your non-Qt based bindings, except for research and (weird) fun purposes. Anyhow, take a look at the Binding Generator page to see how things work and some explanation of the limitations and how we intend to overcome them.

Create your own Binding Generator for your target language of choice

So, you’re thinking in creating a binding generator to make C/C++ libraries available on your heart’s high-level language? Then we have a good kick start for you. The Binding Generator we provide is a front-end that relies on API Extractor, which is the tool that does the hard work of parse the headers, read the XML descriptions of changes, merging all this and delivering well chewed data about the library to be wrapped for the high level target language.

In short, to create a new generator you need to know the API Extractor way of doing things (and your target high level language, of course) and write a generator front-end for it. Also, a good look on our current Binding Generator will be of much help.

Fix things, Contribute Code

If you want to contribute with the project in any way then help yourself to API Extractor and Binding Generator pages. And when contributing code don’t forget: check license, copyrights and all this legal stuff before sending code.