Skip to content

chore: switch build backend to uv #527

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: switch build backend to uv #527

wants to merge 1 commit into from

Conversation

gruebel
Copy link
Member

@gruebel gruebel commented Jul 24, 2025

This PR

  • switched build backend from hatch to uv
  • pinned the uv version to 0.8.x to be better control updates
  • enabled uv.lock updates via renovate
  • some minor cleanup

Signed-off-by: gruebel <anton.gruebel@gmail.com>
@gruebel gruebel requested review from a team as code owners July 24, 2025 22:03
Copy link

codecov bot commented Jul 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.81%. Comparing base (a5b3aa9) to head (b3f1506).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #527      +/-   ##
==========================================
- Coverage   97.85%   97.81%   -0.04%     
==========================================
  Files          38       38              
  Lines        1814     1786      -28     
==========================================
- Hits         1775     1747      -28     
  Misses         39       39              
Flag Coverage Δ
unittests 97.81% <ø> (-0.04%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@beeme1mr
Copy link
Member

Hey @gruebel, thanks for the PR. I've heard good things about uv. It's a silly question, but what's the best way to manually test this? 😰

@gruebel
Copy link
Member Author

gruebel commented Jul 27, 2025

@beeme1mr depending on what you want to test exactly you can build it locally.

uv build

this creates a wheel and a sdist folder under dist and this can be used to install in a separate virtual environment or you could replace it in of our contrib projects. they are still using hatch so you would need to adjust the dependencies block in the pyproject.toml

dependencies = [
  "openfeature-sdk @ file:///[path to the repo]/dist/openfeature_sdk-0.8.1-py3-none-any.whl",
  ...
]

and then you can run in that subproject folder hatch test, if you already had a hatch env setup, then you should uninstall it first

hatch env remove default

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants