Zanie Blue
Zanie Blue
Do you know if pip includes an opt-out for this? (just wondering)
(We should do this)
Good point! I had some fun with this at my last job... https://github.com/PrefectHQ/prefect/blob/4da5da207b126639998917cb1e246f7b15484405/.github/workflows/docker-images.yaml#L110-L116
@nikpivkin that's documented at https://docs.astral.sh/uv/getting-started/installation/#github-releases
Using `>=3.12` is best practice for `requires-python` — it's generally not great to add upper version pins to the Python requirement of the project. Instead, you should use `uv python...
Thanks for the thorough comment @edmorley — I basically agree there are problems with using `>=` for unpublished packages. I think it'd be reasonable to use `==X.y.*` instead, but I...
@Seazs thanks for the report, that's different than this issue — that's a bug. We'll track it in https://github.com/astral-sh/uv/issues/7637
Hi @tkukushkin perhaps that's a tox-uv bug? It sounds like they should be supplying an explicit Python version to use during testing?
Except it doesn't duplicate it — it serves a distinct purpose, e.g., see discussion in https://github.com/astral-sh/uv/issues/8247 You don't need to have a `.python-version` file if you don't want to, but...
@ofer-pd that's addressed a few comments up https://github.com/astral-sh/uv/issues/7429#issuecomment-2543194925 If you're publishing a package, then you should definitely still use a `requires-python` field.