ci: use uv, require recent nox (#394)

* ci: try using a bit of uv

Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>

* chore: use uv if available in noxfile

Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>

* docs: add mentions of uv and pixi

Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>

* Update docs/pages/tutorials/dev-environment.md

---------

Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>

Author: henryiii

.github/workflows/reusable-cookie.yml

@@ -37,8 +37,13 @@ jobs:
           python-version: ${{ matrix.python-version }}
           allow-prereleases: true
 
+      - name: Setup uv
+        uses: yezz123/setup-uv@v4
+        with:
+          uv-venv: ".venv"
+
       - name: Install nox
-        run: pip install nox
+        run: uv pip install nox
 
       - name: Test setuptools
         run: nox -s 'tests(setuptools, novcs)' -s 'tests(setuptools, vcs)'
@@ -97,64 +102,77 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          allow-prereleases: true
+
+      - name: Setup uv
+        uses: yezz123/setup-uv@v4
+        with:
+          uv-venv: ".venv"
+
+      - name: Install nox
+        run: uv pip install nox
+
       - name: Test setuptools
         run: |
-          pipx run nox -s 'nox(setuptools, vcs)'
-          pipx run nox -s 'nox(setuptools, vcs)' -- docs
+          nox -s 'nox(setuptools, vcs)'
+          nox -s 'nox(setuptools, vcs)' -- docs
 
       - name: Test pybind11
         run: |
-          pipx run nox -s 'nox(pybind11, vcs)'
-          pipx run nox -s 'nox(pybind11, vcs)' -- docs
+          nox -s 'nox(pybind11, vcs)'
+          nox -s 'nox(pybind11, vcs)' -- docs
 
       - name: Test scikit-build
         run: |
-          pipx run nox -s 'nox(skbuild, vcs)'
-          pipx run nox -s 'nox(skbuild, vcs)' -- docs
+          nox -s 'nox(skbuild, vcs)'
+          nox -s 'nox(skbuild, vcs)' -- docs
 
       - name: Test poetry
         run: |
-          pipx run nox -s 'nox(poetry, novcs)'
-          pipx run nox -s 'nox(poetry, novcs)' -- docs
+          nox -s 'nox(poetry, novcs)'
+          nox -s 'nox(poetry, novcs)' -- docs
 
       - name: Test flit
         run: |
-          pipx run nox -s 'nox(flit, novcs)'
-          pipx run nox -s 'nox(flit, novcs)' -- docs
+          nox -s 'nox(flit, novcs)'
+          nox -s 'nox(flit, novcs)' -- docs
 
       - name: Test pdm
         run: |
-          pipx run nox -s 'nox(pdm, vcs)'
-          pipx run nox -s 'nox(pdm, vcs)' -- docs
+          nox -s 'nox(pdm, vcs)'
+          nox -s 'nox(pdm, vcs)' -- docs
 
       - name: Test whey
         run: |
-          pipx run nox -s 'nox(whey, novcs)'
-          pipx run nox -s 'nox(whey, novcs)' -- docs
+          nox -s 'nox(whey, novcs)'
+          nox -s 'nox(whey, novcs)' -- docs
 
       - name: Test maturin
         run: |
-          pipx run nox -s 'nox(maturin, novcs)'
-          pipx run nox -s 'nox(maturin, novcs)' -- docs
+          nox -s 'nox(maturin, novcs)'
+          nox -s 'nox(maturin, novcs)' -- docs
 
       - name: Test hatch
         run: |
-          pipx run nox -s 'nox(hatch, vcs)'
-          pipx run nox -s 'nox(hatch, vcs)' -- docs
+          nox -s 'nox(hatch, vcs)'
+          nox -s 'nox(hatch, vcs)' -- docs
 
       - name: Test setuptools PEP 621
         run: |
-          pipx run nox -s 'nox(setuptools621, vcs)'
-          pipx run nox -s 'nox(setuptools621, vcs)' -- docs
+          nox -s 'nox(setuptools621, vcs)'
+          nox -s 'nox(setuptools621, vcs)' -- docs
 
       - name: Activate MSVC for Meson
         if: runner.os == 'Windows'
         uses: ilammy/msvc-dev-cmd@v1
 
       - name: Test meson-python
         run: |
-          pipx run nox -s 'nox(mesonpy, novcs)'
-          pipx run nox -s 'nox(mesonpy, novcs)' -- docs
+          nox -s 'nox(mesonpy, novcs)'
+          nox -s 'nox(mesonpy, novcs)' -- docs
 
   dist:
     name: Distribution build

docs/pages/guides/gha_basic.md

@@ -261,12 +261,21 @@ And many other useful ones:
   built-in caching.
 - [conda-incubator/setup-miniconda](https://github.com/conda-incubator/setup-miniconda):
   Setup conda or mamba on GitHub Actions.
+- [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi): Set up pixi
+  and install your environment(s). Try `cache: false` if saving/loading the
+  cache is slow.
 - [ruby/setup-ruby](https://github.com/ruby/setup-ruby): Setup Ruby if you need
   it for something.
 - [peter-evans/create-pull-request](https://github.com/peter-evans/create-pull-request):
   Make a new PR with the current changes (more options than just using `gh`).
   You can even auto-merge PRs with `run: gh pr merge --merge --auto "1"`
   afterwards.
+- [yezz123/setup-uv](https://github.com/yezz123/setup-uv): Set up `uv`. Has a
+  handy `uv-venv` option that will also set up and activate a virtual
+  environment for you.
+- [gautamkrishnar/keepalive-workflow](https://github.com/gautamkrishnar/keepalive-workflow):
+  Keep GitHub actions alive for more than 60 days. Not usually needed if you've
+  set up the other suggestions here, like dependabot and pre-commit.
 
 A couple more from Python developers; note these do not provide `vX` moving tags
 like the official actions and most other actions, but instead have `release/vX`
@@ -276,6 +285,8 @@ branches that you can use.
   Publish Python packages to PyPI. Supports trusted publisher deployment.
 - [re-actors/alls-green](https://github.com/re-actors/alls-green): Tooling to
   check to see if all jobs passed (supports allowed failures, too).
+- [sigstore/gh-action-sigstore-python](https://github.com/sigstore/gh-action-sigstore-python):
+  Signing files in GitHub Actions with sigstore.
 
 There are also a few useful tools installed which can really simplify your
 workflow or adding custom actions. This includes system package managers (like

docs/pages/guides/tasks.md

@@ -80,7 +80,7 @@ action:
 
 You can now access all current versions of Python from nox. At least in GitHub
 Actions, you should add `--forcecolor` to your nox runs to get color output in
-your logs, or set `env: FORCE_COLOR: 3`. If you'd like to customise the versions
+your logs, or set `env: FORCE_COLOR: 3`. If you'd like to customize the versions
 of Python prepared for you, then use input like this:
 
 ```yaml
@@ -314,6 +314,36 @@ def build(session: nox.Session) -> None:
 <!-- prettier-ignore-end -->
 <!-- [[[end]]] -->
 
+(Removing the build directory is helpful for setuptools)
+
+### Faster with uv
+
+The [uv](https://github.com/astral-sh/uv) project is a Rust reimplementation of
+pip, pip-tools, and venv that is very, very fast. You can tell nox to use `uv`
+if it is on your system by adding the following to your `noxfile.py`:
+
+```python
+nox.needs_version = ">=2024.3.2"
+nox.options.default_venv_backend = "uv|virtualenv"
+```
+
+You can install `uv` with `pipx`, `brew`, etc. If you want to use uv in GitHub
+Actions, one way is to use this:
+
+```yaml
+- name: Setup uv
+  uses: yezz123/setup-uv@v4
+```
+
+You do not need to set `with: uv-venv: ".venv"` for `nox` to be able to use
+`uv`.
+
+Check your jobs with `uv`; most things do not need to change. The main
+difference is `uv` doesn't install `pip` unless you ask it to. If you want to
+interact with uv, nox might be getting uv from it's environment instead of the
+system environment, so you can install `uv` if `shutil.which("uv")` returns
+`None`.
+
 ### Examples
 
 A standard

docs/pages/tutorials/dev-environment.md

@@ -87,6 +87,16 @@ leave the environment (or just close your shell).
 > If you like a different shell, like fish, there are several `activate`
 > scripts; the default one expects a bash-like shell.
 
+{: .note-title }
+
+> Fast alternative
+>
+> You can also consider the [uv][] package, which is much, much faster version
+> of pip and venv implemented in Rust. Just put `uv` in front of the commands
+> you'd normally use; as long as you use venvs, it should be nearly the same.
+
+[uv]: https://github.com/astral-sh/uv
+
 ### Option 2: Using conda
 
 You can also develop in conda. This is an especially good option if:
@@ -113,6 +123,16 @@ conda activate env_name
 
 To deactivate, use `conda deactivate`, or leave your shell.
 
+> Modern faster alternative
+>
+> You can also consider the [pixi][] package, which is much, much faster version
+> of conda implemented in Rust. It has been completely redesigned to work around
+> projects with a `pixi.toml` file instead of global environments. It's a new
+> way to work (more similar to pdm/hatch/poetry from Python), but very powerful
+> if you learn it.
+
+[pixi]: https://pixi.sh
+
 ## Choosing an Editor
 
 Any plain text editor will serve our purposes for this guide. Bare bones editors

noxfile.py

@@ -24,8 +24,9 @@
 
 import nox
 
-nox.needs_version = ">=2022.1.7"
+nox.needs_version = ">=2024.3.2"
 nox.options.sessions = ["rr_lint", "rr_tests", "rr_pylint", "readme"]
+nox.options.default_venv_backend = "uv|virtualenv"
 
 DIR = Path(__file__).parent.resolve()
 with DIR.joinpath("cookiecutter.json").open() as f:

{{cookiecutter.project_name}}/noxfile.py

@@ -13,7 +13,9 @@
 
 {% endif -%}
 
+nox.needs_version = ">=2024.3.2"
 nox.options.sessions = ["lint", "pylint", "tests"]
+nox.options.default_venv_backend = "uv|virtualenv"
 
 
 @nox.session