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
This fully ties the document building to uv by instructing the user to
build a virtual environment with uv.
This also allows us to remove the requirements.txt, as everything should
run through the pyproject.toml.
Copy file name to clipboardExpand all lines: doc/Development.md
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,15 +27,23 @@ If you are testing a project that *uses* `pyimagej` and need to see how changes
27
27
28
28
## Building the reference documentation
29
29
30
-
PyImageJ documentation is built as a [Sphinx](https://www.sphinx-doc.org/en/master/)-built [ReadTheDocs](https://about.readthedocs.com/) site. The documentation has its own `Makefile` in the `/docs` directory. From there:
30
+
PyImageJ documentation is built as a [Sphinx](https://www.sphinx-doc.org/en/master/)-built [ReadTheDocs](https://about.readthedocs.com/) site.
31
31
32
+
To build the documentation, **you must create a `uv` virtual environment** with the additional development dependencies:
33
+
34
+
```bash
35
+
uv run pip install -e ".[dev]"
32
36
```
37
+
38
+
Then, you can either use the documentation's own `Makefile` in the `/docs` directory:
39
+
40
+
```bash
33
41
make html
34
42
```
35
43
36
-
Alternatively, from the project root:
44
+
Alternatively, from the project root`Makefile`:
37
45
38
-
```
46
+
```bash
39
47
make docs
40
48
```
41
49
@@ -45,18 +53,18 @@ Production documentation is available online at
0 commit comments