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.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,17 +28,17 @@ Features include:
28
28
29
29
## Installation
30
30
31
-
You can install this repository with `pip`, either clone it and run `pip install -e .[dev]` to work on it, or just `pip install https://gitlab.com/rwb27/labthings-fastapi.git`. It will be published on PyPI in the near future, initially as `labthings-fastapi`. It may at some point be renamed to `labthings` v2.
31
+
You can install this repository with `pip install labthings-fastapi`. It may at some point be renamed to `labthings` v2. For the latest development version, either clone it and run `pip install -e .[dev]` to work on it, or just `pip install https://gitlab.com/rwb27/labthings-fastapi.git`.
32
32
33
33
## Developer notes
34
34
35
-
The code is linted with `ruff .`, type checked with `mypy src`, and tested with `pytest`. These all run in CI with GitHub Actions. The codebase is not even `v0.1` yet so it's still subject to summary rearrangement.
35
+
The code is linted with `ruff .`, type checked with `mypy src`, and tested with `pytest`. These all run in CI with GitHub Actions. The codebase is not even `v0.1` yet so it's still subject to summary rearrangement. We recommend a [pre-commit hook] to ensure `ruff` passes on every commit.
36
36
37
37
Dependencies are defined in `pyproject.toml` and can be compiled to `dev-requirements.txt` with:
38
38
```
39
-
uv pip compile --extra dev --extra server pyproject.toml --output-file dev-requirements.txt
39
+
uv pip compile --extra dev pyproject.toml --output-file dev-requirements.txt
40
40
```
41
-
If you're not using `uv`, just regular `pip-compile` from `pip-tools`will do the same thing.
41
+
If you're not using `uv`, just regular `pip-compile` from `pip-tools`should do the same thing.
42
42
43
43
All changes to the codebase should go via pull requests, and should only be merged once all the checks in the `test` job are passing. It is preferable to merge code where the `test-with-unpinned-dependencies` job fails, and deal with the dependency issues in another PR, particularly where the required changes are distinct from the code in the PR.
44
44
@@ -49,3 +49,4 @@ See the [examples folder](./examples/) for a runnable demo.
0 commit comments