Move tooling to uv like main altair repo

Author: joelostblom

.github/workflows/build.yml

@@ -15,10 +15,11 @@ jobs:
         uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
-      - name: Install dependencies
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+      - name: Sync dependencies
         run: |
-          python -m pip install --upgrade pip
-          pip install .[dev]
+          uv sync --extra dev
       - name: Test with pytest
         run: |
-          pytest --pyargs --numprocesses=logical tests
+          uv run pytest --pyargs --numprocesses=logical tests

.github/workflows/lint.yml

@@ -12,18 +12,19 @@ jobs:
       uses: actions/setup-python@v5
       with:
         python-version: "3.12"
+    - name: Install uv
+      uses: astral-sh/setup-uv@v6
     # Installing all dependencies and not just the linters as mypy needs them for type checking
-    - name: Install dependencies
+    - name: Sync dependencies
       run: |
-        python -m pip install --upgrade pip
-        pip install hatch
+        uv sync --extra dev
     - name: Lint with ruff
       run: |
-        hatch run ruff check .
+        uv run hatch run ruff check .
     - name: Check formatting with ruff
       run: |
-        hatch run ruff format --diff .
-        hatch run ruff format --check .
+        uv run hatch run ruff format --diff .
+        uv run hatch run ruff format --check .
     - name: Lint with mypy
       run: |
-        hatch run mypy sphinxext_altair tests
+        uv run hatch run mypy sphinxext_altair tests

README.md

@@ -38,28 +38,26 @@ pip install sphinxext-altair
 ```
 
 # Contributing
-It's recommended to use a virtual environment for development:
+It's recommended to use `uv` for development:
 
 ```bash
-python -m venv .venv
-# Install the project in editable mode including development dependencies
-pip install -e '.[dev]'
+uv sync --extra dev
 ```
 
 `sphinxext-altair` uses [ruff](https://github.com/astral-sh/ruff) for code formatting and linting rules, [mypy](https://github.com/python/mypy) for static type checking, and [pytest](https://github.com/pytest-dev/pytest) for testing.   
 All of these tools can be executed by running:
 
 ```bash
-hatch test
+uv run hatch test
 ```
 
 As part of those tests, a Sphinx documentation is built at `tests/roots/test-altairplot`. You can manually build this documentation and view it which is very useful during development of a new feature.
 
 For example, if you want to add a new option to the `altair-plot` directive, you can add another example in the file `tests/roots/test-altairplot/index.rst` and then build and view the documentation by running:
 
 ```bash
-hatch run doc:clean-build-html
-hatch run doc:serve
+uv run hatch run doc:clean-build-html
+uv run hatch run doc:serve
 ```
 
 The test documentation can now be viewed at [http://localhost:8000](http://localhost:8000).

RELEASING.md

@@ -13,7 +13,7 @@
 
 4. Run test suite again after commit above to make sure everything passes:
 
-        hatch run test
+        uv run hatch test
 
 5. Tag the release:
 
@@ -22,12 +22,12 @@
 
 6. Build source & wheel distributions:
 
-        hatch clean  # clean old builds & distributions
-        hatch build  # create a source distribution and universal wheel
+        uv run hatch clean  # clean old builds & distributions
+        uv run hatch build  # create a source distribution and universal wheel
 
 7. publish to PyPI (Requires correct PyPI owner permissions):
 
-        hatch publish
+        uv run hatch publish
 
 8. update version to e.g. 0.3.0dev in `sphinxext_altair/__init__.py`