Zanie Blue
Zanie Blue
Before https://github.com/astral-sh/ruff/pull/22044, this was the best commit from https://github.com/astral-sh/ruff/pull/22052 but now the rest of https://github.com/astral-sh/ruff/pull/22052 looks more promising again 🙃 This commit alone looks like ~no difference on pydantic locally...
After rebasing on `main` the sphinx memory difference went away and now there's a diff on prefect, feeling wary.
I'm doing that, and the diff in sphinx went away :p I also can't see a diff in Prefect locally.
This looks wrong, I'll keep poking in the background.
Oh does it? It looked like it caused some new problems too :)
@MichaReiser CI is green now 🤔
This proposal applies to both the `uv pip` interface (though it would differ from the upstream) and top-level interface (where `--constraint` and `--override` is only implemented for `uv tool install`...
> You could always check for a file first and then fall back to see if it's a valid version specifier This is the behavior we have historically avoided. We...
> Okay but constraints.txt is a valid requirement 😉. Yeah so that's why I said we'd require a version specifier. A constraint without a version specifier doesn't do anything. >...
Alas. I'm not sure what to do about that. As a minor note, it's `UV_CONSTRAINT`. One alternative option: we could align on the name in the `pyproject.toml`, which would be...