Migrate to uv #2455
Migrate to uv #2455
Conversation
|
@colinjc, We do not currently have issues with pip/setuptools so there needs to be a rationale for moving to uv. I may assume it may be beneficial for using in CI if it speeds up installation. Any numbers on that compared to dstack pip installation times? If you gonna proceed with the PR, CONTRIBITING should be updated to use uv, as well as all GitHub actions. |
|
Answering my own question: dstack installation time in CI went from 1m to 5s, which is substantial improvement. |
Also makes checking out the repo for the first time to contribute much faster!
Done |
|
@colinjc, I don't have a time for a thorough review atm, but the PR certainly has some TODOs and is not ready for a merge. I think someone from the core team will be able to move it forward in a few weeks. |
|
Made a few changes and fixes and merged. Works great for development and CI. Also tested @colinjc thanks a lot for the initiative! |
* Migrate to pyproject.toml * Include server extras in backends extras * Use uv for release workflow * Mention uv sync --all-extras --active * Remove --frozen * Use uv to publish to pypi * Replace pip with uv in actions * Require httpbin to be compatible with Werkzeug 3 --------- Co-authored-by: Victor Skvortsov <[email protected]>
Was curious about the level of effort this would take with Cursor and got bored, so here's a quick and dirty attempt to moving over to uv.