build(DRAFT): Migrate from hatch to uv

[dangotbanned]

Will close #3577

Important

A good chunk of the work is done, and uv is working.
Currently supporting both hatch and uv, temporarily.

Description

This PR paves the way for us to switch over to uv, with a solution for the issue I raised in (#3577 (comment)).

Using uv

Install uv for the first time or run:

uv self update

Install python:

uv python install 3.12

Go to the root of the repo:

cd altair/

Initialize a new virtual env:

uv venv -p 3.12 --seed

Install/update dependencies:

uv sync --all-extras

Task Runner

Right now, we can run "tasks" like:

uv run tools/tasks.py test

These can be arbitrarily combined like:

uv run tools/tasks.py generate-schema-wrapper update-init-file

I've tried my best to leave as many options open for us as possible.
You can define "tasks" programatically:

from tools._tasks import Tasks, Commands

app = Tasks(runner="uv")

@app.task()
def my_task() -> Commands:
    yield 'python -c "print(\"doing some work!\")"'
    yield "ruff check ."
    yield "pytest"

# Other tasks can refer to any previously declared tasks
@app.task()
def my_other_task() -> Commands:
    yield "my_task"
    yield "ruff format"

The other interface is demonstrated in tasks.toml.

Generating tasks.toml itself is also expressed as a "task":

altair/tools/tasks.py

Lines 219 to 222 in aaca9bc

	@app.task("export-tasks")
	def export_tasks() -> Commands:
	TASKS_TOML = "tasks.toml"
	yield cmd("from tools.tasks import app", f"app.to_path({TASKS_TOML!r})")

Future

Depending on if (astral-sh/uv#5903) takes a while to resolve, we can easily swap out tools.tasks.py for something like:

• https://github.com/wntrblm/nox
• https://github.com/casey/just
• https://github.com/omnilib/thx

Note

This was pretty fun to work on, but is really just intended as a stepping stone towards using another tool.

---

TODO

The remaining work AFAIK:

• Remove unused hatch config from pyproject.toml (e8d57cd)
• Replace build/publish commands (9900aa1)
  • hatch clean
  • hatch build
  • hatch publish
• Someone w/ permissions to test sync_website.py (https://github.com/altair-viz/altair-viz.github.io)
  • (thread)
• Update docs
  • RELEASING.md
  • NOTES_FOR_MAINTAINERS.md
  • CONTRIBUTING.md
  • README.md

[dangotbanned]

FIXME

@mattijn I was wondering if you might be able to help me with this?
Looking at altair-viz.github.io(contributors), it seems like you've run these steps the most.

All the steps up this sequence are working:

altair/doc/sync_website.sh

Lines 24 to 27 in 48e976e

	# add commit, and push to github
	git add . --all
	git commit -m "$MSG"
	git push origin master

These are the equivalent (with --force (404bb26)):

altair/tools/sync_website.py

Lines 33 to 35 in aaca9bc

	CMD_ADD = "git add . --all --force"
	CMD_COMMIT = "git commit -m"
	CMD_PUSH = "git push origin master"

Which are run in:

add_commit_push_github()

altair/tools/sync_website.py

Lines 106 to 113 in aaca9bc

	def add_commit_push_github(msg: str, /) -> None:
	os.chdir(DOC_REPO_DIR)
	print("Pushing ...")
	# NOTE: Ensures the message uses cross-platform escaping
	cmd_commit = *CMD_COMMIT.split(" "), msg
	commands = (CMD_ADD, cmd_commit, CMD_PUSH)
	for command in commands:
	run_check(command)

Problem

Delete L146-L149 and it produces an error that I'm unsure how to solve.
AFAIK, it didn't seem to be related to permissions on https://github.com/altair-viz/altair-viz.github.io - but that is a blocker I'm expecting

---

RELEASING.md

altair/RELEASING.md

Lines 37 to 54 in 48e976e

	7. Merge release branch into main, make sure that all required checks pass
	8. On main, build source & wheel distributions. If you work on a fork, replace `origin` with `upstream`:
	git switch main
	git pull origin main
	hatch clean # clean old builds & distributions
	hatch build # create a source distribution and universal wheel
	9. publish to PyPI (Requires correct PyPI owner permissions):
	hatch publish
	10. build and publish docs (Requires write-access to altair-viz/altair-viz.github.io):
	hatch run doc:publish-clean-build
	11. On main, tag the release. If you work on a fork, replace `origin` with `upstream`: