Zanie Blue

This exists already as a `Private :: Do Not Upload` [classifier](https://pypi.org/classifiers/)

This is mentioned over in https://github.com/python-poetry/poetry/issues/1537#issuecomment-1154642727 — we might want to include a private mode that avoids attempting to upload to the registry at all. cc @konstin

> The only blocker for this is that currently, uv publish is independent of pyproject.toml: We will upload the files you hand uv publish and if you hand it a...

Yeah I agree, I don't think we need to _require_ it. We could always add a flag that requires we can find it; for people that are concerned about accidentally...

You might want to use `uv tree` to debug your dependency install failures instead?

Interesting. Thanks for sharing. I guess we could add something like `[tool.uv.source-definitions]` then allow `tool.uv.sources. = { definition = ... }` It certainly adds some complexity though, so I'm hesitant...

I'll start working on this.

So I got the builds working on macOS (woo) but I don't know how to tag them? If we have `cpython-3.13.0rc2-aarch64-apple-darwin-noopt-20240907T1906.tar.zst` how are we supposed to add a free-threaded tag?...

👍 cool thanks, that makes sense per the description at https://gregoryszorc.com/docs/python-build-standalone/main/running.html#obtaining-distributions We'll need to figure out the ux in uv, I believe right now we only expose one build option...

That's surprising. Can you share the `--verbose` logs for `uv venv`? It may be helpful to include trace logs which include additional information about interpreter selection `RUST_LOG=uv=trace`