Skip to content

[TOOLING] migrate to uv #502

@aepfli

Description

@aepfli

We recently adopted the openfeature Python SDK within our company and added a wrapper around the flagd provider.
We discovered uv for setting up the project and handling all the build-related tools, which felt nice, easy, and really comfortable. So far, everyone loves it from the tooling side, and it also seems like the current way to go within the Python universe, with ty on the horizon as a fast type checker.

The migration from hatch to UV should be pretty straightforward, as `UV' also uses hatchling by default.

I suggest that we migrate to UV within our Python packages to make adaptation and running the project easier. This issue is to talk about it, and discuss it. There are for sure some trade-offs, but so far I highly enjoyed working with uv way more than working with hatch.

Please feel free to add your thoughts, please don't start any implementation as I think we should first discuss, and I am also keen on trying my luck :)

https://github.com/astral-sh/uv

Metadata

Metadata

Assignees

No one assigned

    Labels

    communityImproving the community and contributor experienceenhancementNew feature or requesthack.commit.pushhelp wantedExtra attention is needed

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions