Backport trivial changes and release python bindings 2.5.1?
Since there is a v2.5.1 release of preCICE we technically should also offer a corresponding release of the python bindings. To wrap-up the version 2 release cycle I think we could also backport the following fixes:
- ~~https://github.com/precice/python-bindings/pull/199~~
- https://github.com/precice/python-bindings/pull/180
- https://github.com/precice/python-bindings/pull/186
- https://github.com/precice/python-bindings/pull/177
- https://github.com/precice/python-bindings/pull/207
- https://github.com/precice/python-bindings/pull/213
- https://github.com/precice/python-bindings/commit/a6d3a80222f85f8c0d87be755ea445d20b721fa3
- https://github.com/precice/python-bindings/pull/215
I came up with this list after a very brief inspection of the features contained in the current latest release. Using the three digit versioning scheme makes everything clearer and, therefore, I see here quite a benefit on the long run. If backporting some of the features/fixes above single turns out problematic, we can, of course, just drop it.
Don't update the versioning scheme, because it too risky and might be confusing.
Added https://github.com/precice/python-bindings/pull/207 and https://github.com/precice/python-bindings/pull/213 to the list due to compatibility problems.
Added https://github.com/precice/python-bindings/commit/a6d3a80222f85f8c0d87be755ea445d20b721fa3 and https://github.com/precice/python-bindings/pull/215 to fix the spack testing for this release.
I just did the release (see #212)