buiild: switch from poetry to uv

Author: mcous

.github/actions/setup/action.yml

@@ -5,12 +5,6 @@ inputs:
     python-version:
         description: "Python version to install"
         default: "3.12"
-    poetry-version:
-        description: "Poetry version to install"
-        default: "2.2.1"
-    cache:
-        description: "Cache directory"
-        default: "${{ runner.temp }}/cache"
 
 runs:
     using: "composite"
@@ -22,39 +16,12 @@ runs:
               python-version: ${{ inputs.python-version }}
               update-environment: false
 
-        - name: "Set up Python 3.12 for Poetry"
-          id: setup-poetry-python
-          uses: actions/setup-python@v5
-          with:
-              python-version: 3.12
-
-        - name: "Set up dependency cache"
-          uses: actions/cache@v4
-          with:
-              key: ${{ runner.os }}-${{ steps.setup-poetry-python.outputs.python-version }}-${{ steps.setup-python.outputs.python-version }}-${{ inputs.poetry-version }}-${{ hashFiles('poetry.lock') }}
-              path: ${{ inputs.cache }}
-
-        - name: "Set up PATH on POSIX"
-          if: ${{ runner.os != 'windows'}}
-          shell: bash
-          run: echo "${{ inputs.cache }}/tools/bin" >> $GITHUB_PATH
-
-        - name: "Set up PATH on Windows"
-          if: ${{ runner.os == 'windows'}}
-          shell: bash
-          run: echo "${{ inputs.cache }}/tools/Scripts" >> $GITHUB_PATH
-
-        - name: "Install Poetry"
-          shell: bash
-          run: |
-              if ! poetry --version; then
-                "${{ steps.setup-poetry-python.outputs.python-path }}" -m venv "${{ inputs.cache }}/tools"
-                pip install poetry==${{ inputs.poetry-version }}
-              fi
+        - name: Install uv
+          uses: astral-sh/setup-uv@681c641aba71e4a1c380be3ab5e12ad51f415867 # v7.1.6
 
         - name: "Install development dependencies"
           shell: bash
+          env:
+              python_path: ${{ steps.setup-python.outputs.python-path }}
           run: |
-              poetry config cache-dir "${{ inputs.cache }}/poetry"
-              poetry env use "${{ steps.setup-python.outputs.python-path }}"
-              poetry sync --all-groups
+              uv sync --all-groups --python "$python_path"

.github/dependabot.yml

@@ -7,7 +7,7 @@ updates:
           interval: "weekly"
           day: "sunday"
 
-    # Poetry dependencies
+    # Python dependencies
     - package-ecosystem: "pip"
       directory: "/"
       schedule:

.github/workflows/ci.yml

@@ -25,9 +25,8 @@ jobs:
                       python-version: "3.7"
                     - os: windows-latest
                       python-version: "3.7"
-                    # TODO: re-enable macOS + Python 3.7 once off Poetry
-                    # - os: macos-15-intel
-                    #   python-version: "3.7"
+                    - os: macos-15-intel
+                      python-version: "3.7"
 
         steps:
             - name: "Check out repository"
@@ -39,7 +38,7 @@ jobs:
                   python-version: ${{ matrix.python-version }}
 
             - name: "Run tests"
-              run: poetry run poe test-ci
+              run: uv run poe test-ci
 
             - name: "Upload coverage report"
               uses: codecov/codecov-action@v5
@@ -57,7 +56,7 @@ jobs:
               uses: ./.github/actions/setup
 
             - name: "Check types, lints, and formatting"
-              run: poetry run poe check-ci
+              run: uv run poe check-ci
 
     build-package:
         name: Build package
@@ -71,7 +70,7 @@ jobs:
               uses: ./.github/actions/setup
 
             - name: "Build"
-              run: poetry run poe build-package
+              run: uv run poe build-package
 
             - name: "Upload"
               uses: actions/upload-artifact@v6
@@ -91,7 +90,7 @@ jobs:
               uses: ./.github/actions/setup
 
             - name: "Build"
-              run: poetry run poe build-docs
+              run: uv run poe build-docs
 
             - name: "Upload"
               uses: actions/upload-pages-artifact@v4

CONTRIBUTING.md

@@ -4,45 +4,43 @@ All contributions are greatly appreciated! Before contributing, please read the
 
 ## Development Setup
 
-This project uses [Poetry][] to manage dependencies and builds, and you will need to install it before working on Decoy.
+This project uses [uv][] to manage dependencies and builds, and you will need to install it before working on Decoy.
 
-Once Poetry is installed, you should be good to set up a virtual environment and install development dependencies. Python >=3.10 is recommended for development.
+Once `uv` is installed, you should be good to set up a virtual environment and install development dependencies. Python >=3.10 is recommended for development.
 
 ```bash
 git clone https://github.com/mcous/decoy.git
 cd decoy
-poetry install
+uv sync
 ```
 
 ## Development Tasks
 
 Decoy uses [poethepoet][] to manage development tasks. If you want to quickly check everything, run the following:
 
 ```shell
-poetry run poe all
+uv run poe all
 ```
 
-[poethepoet]: https://github.com/nat-n/poethepoet
-
 ### Tests
 
 Decoy's tests are run using [pytest][]. To run tests in watch mode:
 
 ```bash
-poetry run poe test
+uv run poe test
 ```
 
 To run tests once and report coverage
 
 ```bash
-poetry run poe test-once
-poetry run poe coverage
+uv run poe test-once
+uv run poe coverage
 ```
 
 In an exciting twist, since version 1.6.0, Decoy's tests rely on Decoy itself to test (and more importantly, design) the relationships between Decoy's internal APIs. This means:
 
--   Decoy's unit test suite serves as an end-to-end test of Decoy by virtue of existing (wow, very meta, actually kind of cool).
--   Changes that break a small part of Decoy may result in a large number of test failures, because if Decoy breaks it can't be used to test itself.
+- Decoy's unit test suite serves as an end-to-end test of Decoy by virtue of existing (wow, very meta, actually kind of cool).
+- Changes that break a small part of Decoy may result in a large number of test failures, because if Decoy breaks it can't be used to test itself.
 
 If you find yourself in a situation where Decoy's test suite has blown up, **concentrate on getting the test suites that don't use Decoy to pass**. From there, lean on the type-checker to guide you to any components that aren't properly hooked up. Decoy also has a end-to-end smoke test suite (`tests/test_decoy.py`) that can be helpful in getting things back to green.
 
@@ -51,17 +49,17 @@ If you find yourself in a situation where Decoy's test suite has blown up, **con
 Decoy's source code is typechecked with [mypy][] and linted/formatted with [ruff][].
 
 ```bash
-poetry run poe check
-poetry run poe lint
-poetry run poe format
+uv run poe check
+uv run poe lint
+uv run poe format
 ```
 
 ### Documentation
 
 Decoy's documentation is built with [mkdocs][], which you can use to preview the documentation site locally.
 
 ```bash
-poetry run docs
+uv run poe docs
 ```
 
 ## Deploying
@@ -77,7 +75,7 @@ git pull
 
 # bump the version
 # replace ${bump_version} with a bump specifier, like "minor"
-poetry version ${bump_version}
+uv version --bump ${bump_version}
 
 # add the bumped pyproject.toml
 git add pyproject.toml
@@ -89,8 +87,9 @@ git tag -a v${release_version} -m "chore(release): ${release_version}"
 git push --follow-tags
 ```
 
+[uv]: https://docs.astral.sh/uv/
+[poethepoet]: https://github.com/nat-n/poethepoet
 [code of conduct]: https://github.com/mcous/decoy/blob/main/CODE_OF_CONDUCT.md
-[poetry]: https://python-poetry.org/
 [pytest]: https://docs.pytest.org/
 [pytest-xdist]: https://github.com/pytest-dev/pytest-xdist
 [mypy]: https://mypy.readthedocs.io

README.md

@@ -22,14 +22,7 @@ Decoy mocks are **async/await** and **type-checking** friendly. Decoy is heavily
 ## Install
 
 ```bash
-# pip
 pip install decoy
-
-# poetry
-poetry add --dev decoy
-
-# pipenv
-pipenv install --dev decoy
 ```
 
 ## Setup