Revision history [back]

Iijoki update seems to break PyOtherSide's call_sync. It's fixed recently in the upstream development version, but no release yet.

https://github.com/thp/pyotherside/issues/49

This is a big deal as call_sync is one of the main functions for interfacing with Python -- I use it especially in QML to read values of configuration options stored in Python and there's no easy way to work around the problem.

Please pull the commit from upstream. Reverting to a pre-Iijoki version (1.3 or 1.2?) would be fine with me as well, but I don't about other features or bugs.

Iijoki update seems to break PyOtherSide's call_sync. It's fixed recently in the upstream development version, but no release yet.

https://github.com/thp/pyotherside/issues/49

This is a big deal as call_sync is one of the main functions for interfacing with Python -- I use it especially in QML to read values of configuration options stored in Python and there's no easy way to work around the problem.

Please pull the commit from upstream. Reverting to a pre-Iijoki version (1.3 or 1.2?) would be fine with me as well, but I don't know about other features or bugs.

Iijoki update seems to break PyOtherSide's call_sync. It's fixed recently in the upstream development version, but no release yet.

https://github.com/thp/pyotherside/issues/49

This is a big deal as call_sync is one of the main functions for interfacing with Python -- I use it especially in QML to read values of configuration options stored in Python and there's no easy way to work around the problem.

Please pull the commit from upstream. Reverting to a pre-Iijoki version (1.3 or 1.2?) would be fine with me as well, but I don't know about other features or bugs. Pre-Iijoki 1.4.4 doesn't seem to work either, something else must have triggered the bug?