[harveymmaunders]

Summary

Moves the Python REST and WebSocket client samples from requirements.txt / dev-requirements.txt + pip to pyproject.toml + uv.lock, managed with uv.

Changes

• pyproject.toml for both samples: runtime deps in [project.dependencies], test/lint tools in a dev dependency group (PEP 735). Versions are unchanged from the old requirements files. uv.lock and .python-version are committed.
• WebSocket project name: the project is named python-websockets-client-sample because a project called websockets clashes with the websockets test dependency.
• requires-python = ">=3.11" to match the CI matrix (3.11–3.15). The READMEs previously said both 3.9+ and 3.10+.
• CI (python-base-ci.yml): uses astral-sh/setup-uv with the matrix Python version and caching, then uv sync --locked, uv run pytest and uv run black --check. There are no pip steps left.
• Dependabot: the Python entries use the uv ecosystem instead of pip.
• READMEs: uv is the main setup route (uv sync / uv run ...), with a plain pip fallback for people who don't use uv:

  python -m venv .venv && . .venv/bin/activate
  python -m pip install --upgrade pip   # needs pip >= 25.1 for --group
  pip install . --group dev

Testing

• uv run pytest tests/ and uv run black --check . pass on Python 3.15 and 3.11 for both samples (REST: 7 tests, WebSockets: 4 tests).
• In a fresh Python 3.11 venv with no uv, pip install . --group dev followed by pytest passes for both samples.

🤖 Generated with Claude Code