Zanie Blue

@contang0 I couldn't reproduce that on my machine ``` ❯ uv init --no-workspace example Initialized project `example` at `/Users/zb/workspace/uv/example` ❯ cd example ❯ ls README.md hello.py pyproject.toml ❯ UV_PROJECT_ENVIRONMENT=/tmp/foo uv...

While I agree for the policy part, that doesn't make sense for the `UV_PROJECT_ENVIRONMENT` behavior — path determination for the environment should not be platform specific (and is tested on...

@contang0 that is explicitly not supported, please see https://github.com/astral-sh/uv/pull/6834 and #1495 — let's stop talking about unrelated questions in this issue though.

Using older versions of build tooling is the primary difference I would presume, though I can't say for sure without trying it out. It's tough to balance the backwards compatibility...

Probably, yes! @arogozhnikov can you test on the a distribution for a newer microarchitecture?

Should also be improved in https://github.com/astral-sh/python-build-standalone/releases/tag/20250106

We don't have a lockfile standard here at uv so I think that the `pip` dependabot backend should just work? I'm not sure there's more for us to do at...

See #6236 — basically it's not supported yet. I think they're working on it still. Renovate supports this.

Thank you for reaching out! I took a look at that pull request (in Dependabot) and it looks better. What uv version was the lockfile generated with originally? We may...

On a separate note, I see you're testing against a dependency that is _also_ pinned in the `pyproject.toml` ```diff --- a/pyproject.toml +++ b/pyproject.toml @@ -5,6 +5,6 @@ description = "Add...