swith to uv

[ClementPinard]

Pull Request

Describe your changes

Bye bye poetry, hello uv !

Issue number if applicable

Checklist before requesting a review

Github actions will check that these tasks were performed but it will reduce friction if you deal with them beforhand

• If code is added, the new lines are covered by tests (Checked by Codecov)
• Type hints are consistent (Checked by pyright Job)
• Code style follows black conventions (Checked by pre-commit)
• If documentation is added, it does not raise a warning in sphinx (checked by sphinx-build)
• CHANGELOG has been updated if applicable

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[alexandre-xxii]

Hello @ClementPinard :)
What's the reason for switching from Poetry to uv?

As far as I understand, uv aims to be an all-in-one tool and claims to offer better performance.
I don’t have any experience with it, so I’m not sure how reliable or well-maintained it is.
If you’re confident it’s a solid choice, I’m inclined to follow your lead.

[ClementPinard]

I'd say API is pretty clean, and dependency resolution is way faster.

I have to admit that poetry is still a good candidate for package manager, but felt like trying out uv.

Given that it does not change the code at all, we can let the PR as is and re-consider it in the future

[NacerKaciXXII]

@ClementPinard seems to me like we can close this one since UV is now introduced in this PR #111

[ClementPinard]

Yes absolutely!