Feat/uv

[S1ro1]

Description

Moves the whole project to use uv instead of vanilla pip, it makes development process easier with a price of small changes to heroku deploy (adding a preprocessing buildpack as heroku doesn't natively support uv yet)

Also moves the whole configuration to pyproject.toml, enabling development dependencies and also configuring ruff in one place.

All updates are reflected in the readme.

Checklist

Before submitting this PR, ensure the following steps have been completed:

• Run the slash command /verifyruns on your own server.
  • Run the cluster bot on your server:

    python discord-bot.py

  • Start training runs with the slash command /verifyruns.
  • Verify that the bot eventually responds with:

    ✅ All runs completed successfully!
    

    (It may take a few minutes for all runs to finish. In particular, the GitHub
    runs may take a little longer. The Modal run is typically quick.)
    For more information on running a cluster bot on your own server, see
    README.md.

[msaroufim]

i don't think we need to check this file in

[S1ro1]

I'm not sure on this one to be fair, as heroku doesn't support uv by default, we need a preprocessor to generate requirements.txt from uv.lock here

I remember from when I used poetry, having .lock in VCS was the correct practice when producing an executable, not a library.

[msaroufim]

IIRC this was needed for heroku not for the package

[S1ro1]

As mentioned in the previous reply, this gets generated via the buildpack on heroku side.

[msaroufim]

SHould also update the procfile cause that's what heroku will run

[S1ro1]

heroku/heroku-buildpack-python#1616 states that uv has no full support for uv, so basically what this does is just uses uv for the development, heroku would still use the default python worker. We can also stick with the current way in favor of having easier deploy and not having uv for personal development @msaroufim .

Another thing to be possibly done, is to create a custom heroku dependencies which install uv for us, but not really in favour of that.

[msaroufim]

Yeah unfortunately without heroku having better support for uv I feel like this PR adds more complexity for some benefit and I don't feel like it's super worth it yet

[S1ro1]

Absolutely, in that case I'm closing it for now. Will stay with pip as is