chore: get ready for lecture

Signed-off-by: Henry Schreiner <[email protected]>

Author: henryiii

.pre-commit-config.yaml

@@ -14,13 +14,13 @@ repos:
       - id: trailing-whitespace
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.12.10
+    rev: v0.13.2
     hooks:
       - id: ruff-format
         exclude: ^content/week01/cleanup_bessel\.ipynb$
 
   - repo: https://github.com/adamchainz/blacken-docs
-    rev: 1.19.1
+    rev: 1.20.0
     hooks:
       - id: blacken-docs
         additional_dependencies: [black==24.*]

content/week04_package/precommit.md

@@ -40,7 +40,7 @@ Here is a minimal `.pre-commit-config.yaml` file with some handy options:
 ```yaml
 repos:
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: "v4.6.0"
+    rev: "v6.0.0"
     hooks:
       - id: check-added-large-files
       - id: check-case-conflict
@@ -91,7 +91,7 @@ Here is the snippet to add Black to your `.pre-commit-config.yml`:
 
 ```yaml
 - repo: https://github.com/psf/black-pre-commit-mirror
-  rev: "24.8.0"
+  rev: "25.9.0"
   hooks:
     - id: black
 ```
@@ -115,7 +115,7 @@ Jupyter outputs:
 
 ```yaml
 - repo: https://github.com/kynan/nbstripout
-  rev: "0.7.1"
+  rev: "0.8.1"
   hooks:
     - id: nbstripout
 ```
@@ -129,7 +129,7 @@ The MyPy addition for pre-commit:
 
 ```yaml
 - repo: https://github.com/pre-commit/mirrors-mypy
-  rev: "v1.11.2"
+  rev: "v1.18.2"
   hooks:
     - id: mypy
       files: src
@@ -141,15 +141,15 @@ designed to avoid configuration, but you should add configuration. You can also
 add items to the virtual environment setup for MyPy by pre-commit, for example:
 
 ```yaml
-additional_dependencies: [attrs==21.2.0]
+additional_dependencies: [attrs==25.3.0]
 ```
 
 MyPy has a config section in `pyproject.toml` that looks like this:
 
 ```ini
 [tool.mypy]
 files = "src"
-python_version = "3.9"
+python_version = "3.10"
 strict = true
 show_error_codes = true
 enable_error_code = ["ignore-without-code", "redundant-expr", "truthy-bool"]
@@ -189,9 +189,9 @@ failures from plugins updating without updating your pre-commit hook.
 
 ```yaml
 - repo: https://github.com/astral-sh/ruff-pre-commit
-  rev: "v0.6.8"
+  rev: "v0.13.2"
   hooks:
-    - id: ruff
+    - id: ruff-check
       args: ["--fix", "--show-fixes"]
     - id: ruff-format
 ```
@@ -230,7 +230,6 @@ extend-select = [
 ignore = [
   "PLR",    # Design related pylint codes
   "PT004",  # Use underscore for non-returning fixture (use usefixture instead)
-  "ISC001", # Conflicts with formatter
 ]
 flake8-unused-arguments.ignore-variadic-names = true
 isort.required-imports = ["from __future__ import annotations"]
@@ -250,13 +249,12 @@ disable auto-fixing for specific error codes via `unfixable`.
 
 There are other configuration options, such as the `src` list which tells it
 where to look for top level packages (mostly for "I" codes, which also have a
-lot of custom configuration options) {% rr RF003 %}, `typing-modules`, which
-helps apply typing-specific rules to a re-exported typing module (a common
-practice for unifying typing and `typing_extensions` based on Python version).
-There's also a file `exclude` set, which you can override if you are running
-this entirely from pre-commit (default excludes include "build", so if you have
-a `build` module or file named `build.py`, it would get skipped by default
-without this).
+lot of custom configuration options), `typing-modules`, which helps apply
+typing-specific rules to a re-exported typing module (a common practice for
+unifying typing and `typing_extensions` based on Python version). There's also a
+file `exclude` set, which you can override if you are running this entirely from
+pre-commit (default excludes include "build", so if you have a `build` module or
+file named `build.py`, it would get skipped by default without this).
 
 Here are some good error codes to enable on most (but not all!) projects:
 
@@ -303,7 +301,7 @@ spell checkers, this has a list of mistakes it looks for, rather than a list of
 
 ```yaml
 - repo: https://github.com/codespell-project/codespell
-  rev: "v2.3.0"
+  rev: "v2.4.1"
   hooks:
     - id: codespell
       args: ["-L", "sur,nd"]

content/week05_ci/ci.md

@@ -82,7 +82,7 @@ jobs:
           python-version: "3.12"
 
       - name: Install package
-        run: python -m pip install .[test]
+        run: python -m pip install -e.[test]
 
       - name: Test package
         run: python -m pytest
@@ -98,7 +98,7 @@ The `jobs:` dict is the other required key, and it has holds a dict with
 arbitrary keys; we used the name `tests:`, but it could have been `hefalump:`
 instead, it's the unique "id" of the job. Inside each job, you'll at least have
 a `runs-on:` setting that tells GHA which operating system image to run on (like
-`ubuntu-latests`, `ubunutu-22.04`, `macos-latest`, `windows-latest`, etc.) There
+`ubuntu-latests`, `ubunutu-24.04`, `macos-latest`, `windows-latest`, etc.) There
 is also are required `steps:`, containing a list of steps.
 
 GitHub Actions runs each step. Steps have an optional (but nice) `name:`. Then
@@ -168,14 +168,14 @@ example:
 strategy:
   matrix:
     runs-on: [ubuntu-latest, windows-latest]
-    python-version: ["3.9", "3.11"]
+    python-version: ["3.10", "3.13"]
     include:
       - runs-on: macos-latest
-        python-version: "3.10"
+        python-version: "3.11"
 ```
 
-Will generate 5 jobs - ubuntu + 3.9, ubuntu + 3.11, windows + 3.9, windows +
-3.11, and macos + 3.10.
+Will generate 5 jobs - ubuntu + 3.10, ubuntu + 3.13, windows + 3.10, windows +
+3.13, and macos + 3.11.
 
 (Advanced) You can also use this to add a new key to an existing run if all
 pre-defined keys match an existing run.
@@ -190,7 +190,7 @@ There are a lot of useful variables available to you. One to highlight is
 `runner.os`, which will tell you what OS you are on. It is usually better to
 write `if: runner.os == "Linux"` over `if: matrix.runs-on == "ubuntu-latest"`,
 since it is less fragile, especially if you use versioned image runners like
-`ubuntu-22.04`; it also doesn't depend on whatever you named `runs-on` in your
+`ubuntu-24.04`; it also doesn't depend on whatever you named `runs-on` in your
 matrix.
 
 ### Useful things to know
@@ -222,6 +222,10 @@ updates:
     directory: "/"
     schedule:
       interval: "weekly"
+    groups:
+      actions:
+        patterns:
+          - "*"
 ```
 
 This will check to see if there are updates to the action weekly, and will make
@@ -274,22 +278,21 @@ tests:
     fail-fast: false
     matrix:
       python-version:
-        - "3.9"
+        - "3.10"
         - "3.13"
   name: Check Python ${{ matrix.python-version }}
   steps:
     - uses: actions/checkout@v4
 
+    - uses: astral-sh/setup-uv@v6
+
     - name: Setup Python ${{ matrix.python-version }}
       uses: actions/setup-python@v5
       with:
         python-version: ${{ matrix.python-version }}
 
-    - name: Install package
-      run: python -m pip install -e .[test]
-
-    - name: Test package
-      run: python -m pytest
+    - name: Install and test package (using dev group)
+      run: uv run pytest
 ```
 
 A few things to note from above:
@@ -348,6 +351,7 @@ There are a variety of useful actions. There are GitHub supplied ones:
 
 And many other useful ones:
 
+- [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv): Setup uv.
 - [ilammy/msvc-dev-cmd](https://github.com/ilammy/msvc-dev-cmd): Setup MSVC
   compilers.
 - [jwlawson/actions-setup-cmake](https://github.com/jwlawson/actions-setup-cmake):