build(uv): Lean on uv for all tasks within Makefile

[schloerke]

Changes

Breaking changes:

• Drop python 3.8 support
  • Main motivation: uv doesn't like to run quartodoc when python 3.8 is supported. However, python 3.8 is EOL, so it is fair to drop support.
  • Update: Workarounds were made to have quartodoc and uv play nicely. No remaining reason to drop 3.8

UV:

• Require usage of .venv
• Use uv for as many commands as possible
  • Every make command should be able to be run without requiring to activate the virtual environment
  • (Reduce adoption friction down to a minimum)
• Always install deps with uv before a python package command is run
• Remove requirements.txt and requirements-dev.txt. Instead, leverage pyproject.toml
  • Drop make deps and fold functionality into make dev
  • Currently waiting on pip to determine who groups are installed before uv implements group installation: uv pip install --group astral-sh/uv#8590 (comment) . However, uv is fast that groups are not really needed for now.

GHA:

• Use astral-sh/setup-uv and uv python install VERSION to install uv and python
• Remove usage of env: { UV_SYSTEM_PYTHON: true }
• Drop cache from runs. uv is fast to install everything and nothing can get poisoned from prior runs. (Major pain to discover / debug)
• Test on python 3.13

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
1245	1191	96%	0%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
src/posit/connect/paginator.py	100%	🟢
TOTAL	100%	🟢

updated for commit: 8d8c0ae by action🐍

[tdstein]

This is awesome! We'll need to adjust to continue supporting Python 3.8, but otherwise this looks great. It's wild how many new features uv has introduced since we originally migrated to it in August.

[tdstein]

Also, you can remove the '!' from the conventional commit title. The '!' is only necessary for breaking changes affecting package consumers (e.g., a change requiring a major version bump).

"build(uv): lean on uv for all python tasks" would also be appropriate since this affects more than the Makefiles.

[tdstein]

🙌🏻

I have one outstanding question regarding the integration tests, but regardless, this is awesome! I love the pragmatic use of uv in different places. It really shows the power of the tooling.