Comment 9 for bug 1074028

No, the introspection code has been carefully constructed to work excellently with both python 2 and python 3. The static bindings only support python 2, so sticking with the static bindings is holding you back. Porting to introspection doesn't force you to also port to python 3 immediately, what it does is *allows* you to port to Python 3 at your leisure.

The benefit to your users is that your application will continue to exist. Python 2 and GTK 2 are going away. Sure, it might be years before they're truly gone, but it will happen eventually. Imagine for a moment if your application only ran with Python 1 and GTK 1. Nobody would even be able to run it because nobody packages those old versions anymore. They're unsupported, unmaintained, and if you found a bug in the APIs, it would simply never get fixed. Python 2 and GTK 2 are slowly moving in that direction and if you don't port away from them, users will eventually lose the ability to run your program as distros stop shipping those versions.

I am not familiar with gphoto2 specifically, but yes, the introspection bindings are well maintained and if you find bugs in them, you can reasonably expect to report those and get them fixed. So yes, you'll be able to get away from the 'nightmare' of unmaintained, buggy bindings.