python-bindings
python-bindings copied to clipboard
precice
Python language bindings for preCICE
`pyproject.toml` is the current standard for providing metadata and dependency information. Requiring setuptools>=61 (#207) is a step into this direction. See also https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html.
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...
This PR removes the spack-related tests and documentation. Testing the spack package is now an additional optional step in the Release Guide. Closes #220
In tox, one can run disable the automatic installation of the package and run custom commands to setup an environment. This should allow us to build the mock locally, then...
The tests of the python bindings to keep spack working involves many layers as spack used to install packages by calling setup.py as follows: ``` $ python setup.py build $...
`pyproject.toml` is the recommended format and we are mainly using the `setup.cfg` for versioneer. Versioneer also supports `pyproject.toml`. Therefore, moving should be possible. See https://github.com/python-versioneer/python-versioneer?tab=readme-ov-file#vendored-mode.
Backports some trivial changes to v2.5.0. Compatibility release for preCICE [v2.5.1](https://github.com/precice/precice/releases/tag/v2.5.1). Closes #203
I implemented this to build the base environments for testing spack in #212.
Support for the `test` command has been removed in Setuptools 72. Currently, our (mock) tests require this command. We, therefore, need to update our tests to make them futureproof.
Currently, we run the [release](https://github.com/precice/python-bindings/blob/develop/.github/workflows/release.yml) workflow to upload the package to PyPI after creating a tag on GitHub, which is typically associated with a newly released version. If the release...
