This is not a bug. The API does not publicly expose the constructor, i. e. Xkl.Engine.new() does not exist. Xkl.Engine() invokes the GObject constructor on it, which we cannot hide unfortunately.
The API documentation [1] shows that you need to use the singleton function Xkl.Engine.get_instance(display) for this. This works fine, the upstream code has a test script for all this, which you might steal from [2].
This is not a bug. The API does not publicly expose the constructor, i. e. Xkl.Engine.new() does not exist. Xkl.Engine() invokes the GObject constructor on it, which we cannot hide unfortunately.
The API documentation [1] shows that you need to use the singleton function Xkl.Engine. get_instance( display) for this. This works fine, the upstream code has a test script for all this, which you might steal from [2].
[1] http:// xlibs.freedeskt op.org/ xkbdesc/ doc/libxklavier -xkl-engine. html#xkl- engine- get-instance cgit.freedeskto p.org/libxklavi er/tree/ tests/test_ gi.py
[2] http://