[2.1.0.9] PyOtherSide call_sync broken
asked 2017-02-12 03:42:39 +0300
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?
It seems I can work around this in common cases by forming the equivalent
otsaloma ( 2017-02-12 16:11:15 +0300 )editevaluatecall myself, but such custom data type to string transformations are likely to be corner-case bug-prone.Interesting - looks like modRana has not been hit by this due to not doing any synchronous calls at all. But I guess it could be rather hard to change existing code that expects synchronous calls to work with calls that are fully asynchronous.
But in any case this is a serious regression which should be fixed.
MartinK ( 2017-02-12 17:07:45 +0300 )editBTW, I have a merge request open for updating PyOtherSide to 1.5.
I guess the fix for the
MartinK ( 2017-02-13 17:23:56 +0300 )editcall_synccould be also proposed/added in similar way (either to current 1.4 or to 1.5 after/if the update merge request is accepted).