python-template
python-template copied to clipboard
NLeSC
Netherlands eScience Center Python Template
The repo should have a description. See if we can automate this using some GH action or document it.
e.g. test_project, test_value, test_lint should each have a module level docstring stating their purpose; maybe individual tests should, too
Currently, the template is set up to build the package with setuptools. ~~However, the [current advise on packaging.python.org](https://packaging.python.org/en/latest/tutorials/packaging-projects/#creating-pyproject-toml) is to use hatchling. (related to #318)~~ _Edit: The default option is...
**Description** This PR moves the generated package to the `src/` based layout. I think I've propagated this change everywhere necessary, and all tests currently pass. - [x] I have read...
See for instance [DIANNA](https://github.com/dianna-ai/dianna/blob/main/.github/workflows/release.yml).
In the guide, we are updating the recommendations for publishing a python package on pypi with github actions: https://github.com/NLeSC/guide/pull/323. To be consistent, we should also update the corresponding instructions in...
GEMDAT uses GitHub Actions to generate a coverage badge, which is published to a GitHub Gist and from there can be included in the README.md. See https://github.com/GEMDAT-repos/GEMDAT/blob/main/.github/workflows/tests.yaml Something like this...
Covbadge
**Description** This PR adds a workflow based on coverage.py and gists to generate a coverage badge. The advantage of this is that no third party service is needed. Closes #369...
As mentioned [here](https://github.com/GEMDAT-repos/GEMDAT/pull/229#discussion_r1432832057) by @stefsmeets, it might be smarter to use explicit search patterns for finding and replacing the versions using bump-my-version. The default behavior is to just do a...