Update dev setup for uv workflow

Author: Preocts

CONTRIBUTING.md

@@ -38,136 +38,72 @@ prior to submitting a pull request.
 
 ---
 
-# Local developer installation
-
-The following steps outline how to install this repo for local development.
+# Developer installation
 
 ## Prerequisites
 
-### Clone repo
-
-```console
-git clone https://github.com/[ORG NAME]/[REPO NAME]
-
-cd [REPO NAME]
-```
+- [**uv**] >= 0.6.3
 
-### Virtual Environment
+[Installation options can be found here.](https://docs.astral.sh/uv/getting-started/installation/)
 
-Use a ([`venv`](https://docs.python.org/3/library/venv.html)), or equivalent,
-when working with python projects. Leveraging a `venv` will ensure the installed
-dependency files will not impact other python projects or any system
-dependencies.
+Or just use [pipx](https://pypi.org/project/pipx/)
 
-**Windows users**: Depending on your python install you will use `py` in place
-of `python` to create the `venv`.
-
-**Linux/Mac users**: Replace `python`, if needed, with the appropriate call to
-the desired version while creating the `venv`. (e.g. `python3` or `python3.12`)
-
-**All users**: Once inside an active `venv` all systems should allow the use of
-`python` for command line instructions. This will ensure you are using the
-`venv`'s python and not the system level python.
-
-### Create the `venv`:
-
-```console
-python -m venv .venv
+```bash
+pipx install uv
 ```
 
-Activate the `venv`:
 
-```console
-# Linux/Mac
-. .venv/bin/activate
-
-# Windows
-.venv\Scripts\activate
-```
-
-The command prompt should now have a `(venv)` prefix on it. `python` will now
-call the version of the interpreter used to create the `venv`
-
-To deactivate (exit) the `venv`:
+### Clone repo
 
-```console
-deactivate
+```bash
+git clone https://github.com/[ORG NAME]/[REPO NAME]
 ```
 
 ---
 
-## Developer Installation Steps
+## Developer Installation Commands
 
-### Install editable library and development requirements
+### 1. Install editable library and development requirements
 
-```console
-python -m pip install --editable .[dev,test]
+```bash
+uv sync
 ```
 
-### Install pre-commit [(see below for details)](#pre-commit)
+### 2. Install pre-commit [(see below for details)](#pre-commit)
 
-```console
+```bash
 pre-commit install
 ```
 
-### Install with nox
-
-If you have `nox` installed with `pipx` or in the current venv you can use the
-following session. This is an alternative to the two steps above.
-
-```console
-nox -s install
-```
-
 ---
 
-## Pre-commit and nox tools
-
-### Run pre-commit on all files
+## Nox sessions
 
-```console
-pre-commit run --all-files
-```
+This repo uses [nox](https://nox.thea.codes/en/stable/index.html) to simplify
+workflow actions.
 
-### Run tests with coverage (quick)
+### Run tests and report coverage (quick):
 
-```console
-nox -e coverage
+```bash
+nox --session coverage
 ```
 
-### Run tests (slow)
+### Run tests against all supported versions (slow):
 
-```console
+```bash
 nox
 ```
 
-### Build dist
-
-```console
-nox -e build
-```
-
----
-
-## Updating dependencies
-
-New dependencys can be added to the `requirements-*.in` file. It is recommended
-to only use pins when specific versions or upgrades beyond a certain version are
-to be avoided. Otherwise, allow `pip-compile` to manage the pins in the
-generated `requirements-*.txt` files.
-
-Once updated following the steps below, the package can be installed if needed.
-
-### Update the generated files with changes
+### Run pre-commit on all files
 
 ```console
-nox -e update
+nox --session pre_commit
 ```
 
-### Upgrade all generated dependencies
+### Build dist
 
 ```console
-nox -e upgrade
+nox --session build
 ```
 
 ---
@@ -178,9 +114,3 @@ nox -e upgrade
 
 This repo is setup with a `.pre-commit-config.yaml` with the expectation that
 any code submitted for review already passes all selected pre-commit checks.
-
----
-
-## Error: File "setup.py" not found
-
-Update `pip` to at least version 22.3.1