[TASK] Migrate from hatch to uv for developing/contributing

[theagenticguy]

Problem Statement

I'm currently implementing #25 and I have had a tough time with the dev experience using hatch.

• I had to install venv's myself.
• The hatch fmt and hatch run commands weren't very intuitive and hard to debug my lint and test errors.
• Trying to use mypy outside of hatch resulting in not following the mypy config inside pyproject.toml.

uv from Astral fully manages pyproject.toml, manages and installs venv's, installing and managing dependencies and resolution, supports tool configuration, builds, etc. It's also really fast

Proposed Solution

No response

Use Case

I would have a better developer/contributor experience using uv

Alternatives Solutions

No response

Additional Context

No response

[zastrowm]

Hey, thanks for the request! The team is open to switching to uv and would gladly accept community contributions to make the switch, as we're not sure when we would be able to get to this ourselves.

If anyone is interested in picking this up, the requirements would be:

• Update all strands-agents repositories to use uv, including sdk-python, tools, and agent-builder.
• Switch all existing commands that use hatch (formatting, linting, etc.) over to uv.
• Update the GitHub workflows from hatch to uv.
• Update the build documentation to mention uv instead of hatch.

[kenliao94]

Do I just submit a PR if I am interested in taking on this task? Or is there a process that I need to follow?

[awsarron]

PRs are very welcome! Our contribution guide has some details - https://github.com/strands-agents/sdk-python/blob/main/CONTRIBUTING.md.

[brianloyal]

Took a stab at it as well in #77

[zastrowm]

I've been looking at this a bit in my downtime and discussed a bit with the team.

Switching to UV has benefits, but it's not a replacement for hatch as we initially thought. It's more of an alternative to PIP and solving some of the venv problems that the team has encountered.

We think the biggest benefit to uv might be a lock file but I'm just setting expectations that this isn't a replacement to hatch

[theagenticguy]

In case it helps someone, this is my pyproject.toml for doing everything* with uv: https://github.com/theagenticguy/tag-python-starter/blob/main/pyproject.toml

*uv doesn't have a built in task runner like hatch, so I use poethepoet, ref: astral-sh/uv#5903

[Unshure]

Looks like pip has an experimental feature to generate a pylock.toml file: https://pip.pypa.io/en/stable/cli/pip_lock/

Could be a alternative to consider

[Unshure]

Chatted with the team offline on this topic. We decided against using a lock file since we are a vended library. We want to support a range of versions of dependencies, instead of locking down what dependency we use. This will give more flexibility to our consumers.