Confusing versioning of Python package versus Core WebUI

[kvbik]

Starting with 10ebb25 there was an increment from v2.4.1 to v2.4.2, but the Core WebUI used was still v2.4.1, couple commits later the Core was incremented also, but so was the python wrapper to v2.4.3.

I am no expert on building wrappers and semantic version of those, but I find it rather confusing. I understand the need of iterating the Python wrapper over the same Core version. So maybe what was done before, eg.: v2.4.2.X was bit better?

UPDATE: ok, semantic versioning discourages [1] from keeping the same version number for wrapper and the core library. But maybe in our case here it is not that bad - if they don't differe in one number of the scheme CORE.MAJOR.MINOR.PATCH.

[1] semver/semver#352 (comment)

[hassandraga]

Thank you for suggesting that. This is an important point. We tried to standardize all wrappers (Versions, dealing with binaries...), but we found out that each wrapper has different needs, so we decided to let each wrapper follow its path. It's not the final decision, but it's going well for now.

should never pin the FooJS version to the Foo version
[1] semver/semver#352 (comment)