upgrade python backend from poetry to uv

[mishraomp]

https://github.com/astral-sh/uv

[mishraomp]

@franTarkenton @conbrad @DerekRoberts this looks promising, let me know if you guys think otherwise.

[DerekRoberts]

@mishraomp Let's dig in. :)

[conbrad]

Looks interesting, we use their lint/formatter tool, ruff: https://github.com/astral-sh/ruff

[conbrad]

Might be difficult for us to use since we work on macOS, and their lockfiles are platform specific: https://github.com/astral-sh/uv?tab=readme-ov-file#limitations

[conbrad]

Looks like you can generate different platform lockfiles with a flag though so it may not be too tricky: https://github.com/astral-sh/uv?tab=readme-ov-file#platform-independent-resolution

[mishraomp]

thanks @conbrad , may be we should move from poetry and prospector in the qsos to uv and ruff

cc @DerekRoberts @franTarkenton

[DerekRoberts]

Thanks @conbrad. Unfortunately the non-agnostic lockfiles sound like a deal breaker. Rather than using their workarounds, how about waiting until this is solved?

[conbrad]

Thanks @conbrad. Unfortunately the non-agnostic lockfiles sound like a deal breaker. Rather than using their workarounds, how about waiting until this is solved?

I think it should be fine, would just need to test it, from their readme:

For example, if you're running uv on macOS, but want to resolve for Linux, you can run uv pip compile --python-platform=linux requirements.in to produce a manylinux2014-compatible resolution.

[conbrad]

It might even be more transparent than pip, poetry, etc, since their agnostic lockfiles are hiding the real binaries they're pulling down for each platform anyways.