You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrate to pyproject.toml and common workflows, update for numpy 2.0 (#35)
* move to pyproject file
* remove setup.py
* not needed anymore
* using common workflows
* switch to np.nan for numpy 2.0 compatibility
* and bump patch version for release
* and add to changelog
* membership test should be 'not in'
* not fstrings
* update authors metadata as discussed
This package implements different workflows for CI.
3
+
This package implements different workflows for CI, based on our organisation's common workflows.
4
4
They are organised as follows.
5
5
6
6
### Documentation
7
7
8
8
The `documentation` workflow triggers on any push to master, builds the documentation and pushes it to the `gh-pages` branch (if the build is successful).
9
-
It runs on `ubuntu-latest` and Python version, `Python 3.9`.
10
9
11
10
### Testing Suite
12
11
13
12
Tests are ensured in the `tests` workflow, which triggers on all pushes.
14
-
It runs on a matrix of all supported operating systems (ubuntu-20.04, ubuntu-22.04, windows-latest and macos-latest) for all supported Python versions (currently `3.7`, `3.8`, `3.9` and `3.10`).
13
+
It runs on a matrix of all supported operating systems for all supported Python versions.
15
14
16
15
### Test Coverage
17
16
18
17
Test coverage is calculated in the `coverage` wokflow, which triggers on pushes to `master` and any push to a `pull request`.
19
-
It runs on `ubuntu-latest` & the Python version (`Python 3.9`), and reports the coverage results of the test suite to `CodeClimate`,
18
+
It reports the coverage results of the test suite to `CodeClimate`.
20
19
21
20
### Regular Testing
22
21
23
22
A `cron` workflow triggers every Monday at 3am (UTC time) and runs the full testing suite, on all available operating systems and supported Python versions.
24
-
It also runs on `Python 3.x` so that newly released Python versions that would break tests are automatically detected.
23
+
It also runs on `Python 3.x` so that newly released Python versions that would break tests are automatically included.
25
24
26
25
### Publishing
27
26
28
-
Publishing to `PyPI` is done through the `publish` workflow, which triggers anytime a `release` is made of the Github repository.
27
+
Publishing to `PyPI` is done through the `publish` workflow, which triggers anytime a `release` is made of the GitHub repository.
29
28
It builds a `wheel`, checks it, and pushes to `PyPI` if checks are successful.
0 commit comments