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
Copy file name to clipboardExpand all lines: README.dev.md
+38-4Lines changed: 38 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Please follow these steps:
12
12
13
13
1. (**important**) announce your plan to the rest of the community _before you start working_. This announcement should be in the form of a (new) issue;
14
14
1. (**important**) wait until some kind of consensus is reached about your idea being a good idea;
15
-
1. if needed, fork the repository to your own Github profile and create your own feature branch off of the latest master commit. While working on your feature branch, make sure to stay up to date with the master branch by pulling in changes, possibly from the 'upstream' repository (follow the instructions [here](https://help.github.com/articles/configuring-a-remote-for-a-fork/) and [here](https://help.github.com/articles/syncing-a-fork/));
15
+
1. if needed, fork the repository to your own GitHub profile and create your own feature branch off of the latest master commit. While working on your feature branch, make sure to stay up to date with the master branch by pulling in changes, possibly from the 'upstream' repository (follow the instructions [here](https://help.github.com/articles/configuring-a-remote-for-a-fork/) and [here](https://help.github.com/articles/syncing-a-fork/));
16
16
1. make sure the existing tests still work by running `pytest` (see also [here](#testing-locally));
17
17
1. add your own tests (if necessary);
18
18
1. update or expand the documentation;
@@ -31,7 +31,7 @@ readibility or simplicity is more important than absolute correctness.
31
31
It is hard to define the precise balance we are looking for, so instead we will refer
32
32
to the [Zen of python](https://peps.python.org/pep-0020/).
33
33
34
-
Note that all contrubtions to this project will be published under our [Apache 2.0 licence]
34
+
Note that all contributions to this project will be published under our [Apache 2.0 licence]
Test data should reside in the `test_data/` folder in the root of the repository.
108
+
109
+
Alternatively, use zenodo-get to download the data directly into the `test_data/` folder:
110
+
111
+
Using `uv`:
112
+
113
+
```shell
114
+
mkdir -p test_data
115
+
cd test_data
116
+
uv tool run zenodo_get 17423608
117
+
cd -
118
+
```
119
+
120
+
Using `pip`:
121
+
122
+
```shell
123
+
pip install zenodo-get
124
+
mkdir -p test_data
125
+
cd test_data
126
+
zenodo_get 17423608
127
+
cd -
128
+
```
129
+
130
+
131
+
##### Running tests
132
+
101
133
For testing all you need to do is run:
102
134
103
135
```shell
@@ -120,7 +152,9 @@ coverage report
120
152
121
153
We use [ruff](https://docs.astral.sh/ruff/) for linting, sorting imports and formatting of python (notebook) files. The configurations of `ruff` are set in [pyproject.toml](pyproject.toml) file.
122
154
123
-
If you are using VS code, please install and activate the [Ruff extension](https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff) to automatically format and check linting.
155
+
If you are using VS code, please install and activate the [Ruff
156
+
extension](https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff) to automatically format and check
157
+
linting. Make sure to use the ruff version installed in your environment.
124
158
125
159
Otherwise, please ensure check both linting (`ruff fix .`) and formatting (`ruff format .`) before requesting a review.
0 commit comments