Zanie Blue

It's also worth noting in this case, I have moved the release _back_ to a pre-release to investigate a possible regression (ref #405). I'd recommend making your tool robust to...

> From what you are saying it seems that metadata file would be not be part of the release? I think we'd need to run a second action after validating...

Thanks @hugovk That certainly seems better than trying to duplicate the information — a single source of truth seems ideal.

I tested installation into a system environment with: ```dockerfile FROM python:3.11.9-slim-bookworm # Add my locally built binary ADD uv /bin/uv RUN chmod +x /bin/uv # Create a project RUN uv...

@edmorley please let me know if this will work for CNBs — I find that use-case particularly compelling. I also plan to validate this approach works well for multi-stage Docker...

Yes `uv pip install` will ignore this. It's not a part of the "project" interface. _Maybe_ it should support it in a project root (as I did for venv), but...

I think it would make sense to respect `UV_PROJECT_ENVIRONMNET` when using `uv pip install` from a project root as in https://github.com/astral-sh/uv/pull/6835 — but there's a bunch places we'd need to...

> > if you're cooperating with others on a project, you're dictating on them where to put their venv. > > Unfortunately this is a reality in some projects (think...

Responding to the above 1. Yes, you could do that. I wouldn't recommend it, but it seems okay to use this to match your active environment. 2. I don't think...

Yeah totally agree — but that use-case doesn't require uv to read and mutate an "active" virtual environment.