-
Notifications
You must be signed in to change notification settings - Fork 38
[TOOLING] migrate to uv #502
Copy link
Copy link
Closed
Labels
communityImproving the community and contributor experienceImproving the community and contributor experienceenhancementNew feature or requestNew feature or requesthack.commit.pushhelp wantedExtra attention is neededExtra attention is needed
Metadata
Metadata
Assignees
Labels
communityImproving the community and contributor experienceImproving the community and contributor experienceenhancementNew feature or requestNew feature or requesthack.commit.pushhelp wantedExtra attention is neededExtra attention is needed
Type
Projects
Status
Done
We recently adopted the openfeature Python SDK within our company and added a wrapper around the flagd provider.
We discovered
uvfor 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, withtyon the horizon as a fast type checker.The migration from
hatchtoUVshould 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
uvway more than working withhatch.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