[FEATURE] Experiment with using uv as the package manager

[atakanyenel]

This project is using poetry as its package manager. uv is the new hype in Python world, and this project can benefit from using it instead of relying on pip or poetry. This feature request will experiment with uv to see if the migration is simple and if it really benefits the project.

I'm happy to work on this and create a PR with the uv config/docs.

[begumcig]

Hey @atakanyenel, thanks so much for the suggestion! 🙌

We’ve been keeping an eye on uv, it’s a really exciting project, and we love the direction it’s going. Since we currently use poetry across all our projects, switching tooling would affect quite a few areas, so we want to approach it thoughtfully.

That said, we’re definitely open to exploring what a uv-based setup might look like. If you’re up for drafting a PR that adds uv support without disrupting the current poetry flow, that would be a great starting point.

Really appreciate you jumping in and offering to contribute, it means a lot! And if anything comes up while you're working on it, feel free to reach out. Happy to help 💜

[atakanyenel]

Hi begum,
Looks like both uv and poetry uses the pyproject.toml file as their config, so it's not possible to run them side by side. Since you are using poetry for internal projects as well, looks like it's a Company level decision to migrate to uv or not. Nevertheless, here is the steps I did to integrate project with uv:

0. All of this runs on a clean VM with only python installed
1. python version 3.9.21
2. Install uv
3. $ uvx migrate-to-uv
4. $ uv pip install torch
5. $ uv pip install setuptools
6. requires-python changed to ">=3.9"
7. Change licence field to license-files = ["LICENSE"]
8. uvx hatch build works but it doesn't actually include the subpackages into .whl archieve
9. uvx hatch test fails because it can't find the subpackages.