Switch to uv for package management

[jamesmurdza]

This PR changes our monorepo setup to use uv.

This removes the existing build scripts which led to dependency issues due to sequential installation of Cua packages.

Usage

This setup requires no build scripts. You can just run:

uv run python examples/agent_examples.py

(To test that this works, run rm -rf .venv first.)

When you run this:

1. uv runs uv sync. A virtual environment is created if necessary, and packages are installed from uv.lock.
2. The script is run in the new virtual environment

You can also run uv sync to create the virtual environment manually, to use it in VS Code for example.

Changes:

• Migrates pyproject and the corresponding lock file to use uv
• Removes build shell scripts, as they are not needed given uv’s built-in functionality.
• Removes the script to automatically install uv—which saves the user a minor amount of time but brings extra complexity.
• Upgrades the project to Python 3.13
• Fixes a dependency conflict with transformers
• Removes pylume from the pyproject
• Sets defaultInterpreterPath to .venv in VS Code
• Updates the Development guide to reflect the switch to uv

[r33drichards]

this might be redundant step if uv venv .venv --python 3.12 is idempotent, might also make sense to just rm -rf .venv before too if it it might exist to make the test more reproducible and not get bugs due to existing state vs desired state

[r33drichards]

lgtm

[r33drichards]

this overwrites .env, which could be nasty if i have something there i want to keep

[jamesmurdza]

Yeah! We already have this line: https://github.com/trycua/cua/blob/main/.vscode/py.code-workspace#L58C1-L59C1

So I'm thinking that should be enough for VS Code to locate packages?

[jamesmurdza]

@r33drichards My initial solution actually did not work. I have recreated the setup using the uv documentation and a much simpler approach.

[ddupont808]

currently the ./Dockerfile file still uses the old build.sh. this Dockerfile is used by the ./.devcontainer and the ./scripts/run-docker-dev.sh setups. we should replace those with a uv sync or deprecate the containerized development mode

[jamesmurdza]

currently the ./Dockerfile file still uses the old build.sh. this Dockerfile is used by the ./.devcontainer and the ./scripts/run-docker-dev.sh setups. we should replace those with a uv sync or deprecate the containerized development mode

That's a good point. I’d support deprecating the devcontainer, with the option to recreate it quickly if a user requests it of course.