[python] fix install_packages.py: use 'uv build --wheel' instead of non-existent 'uv pip wheel'

[msyyc]

Problem

tests/install_packages.py build <flavor> currently runs:

subprocess.run(["uv", "pip", "wheel", "--no-deps", "--wheel-dir", wheel_dir] + batch, check=True)

But uv pip wheel is not a real uv subcommand. The PipCommand enum only contains compile / sync / install / uninstall / freeze / list / show / tree / check (see crates/uv-cli/src/lib.rs). Reproduced locally on uv 0.11.x:

> uv pip wheel --help
error: unrecognized subcommand 'wheel'

The existing fallback only catches FileNotFoundError, so when uv is present (which it always is in CI via mise), the whole job dies with CalledProcessError.

Fix

• Switch to uv build --wheel --no-build-logs --out-dir <dir> <pkg> (the command that has actually existed since uv 0.4).
• Build per-package instead of in batches of 50, so a single broken pyproject.toml no longer poisons the whole batch.
• Catch CalledProcessError per package, log a warning, and accept partial success — packages that failed to wheelize will be installed from source by install_packages() later.
• Keep the uv->pip wheel fallback for environments where uv is genuinely missing.

This matches the working pattern that Azure/typespec-azure's install_packages.py had before it was overwritten by syncing this file from upstream.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http-client-python@10636

commit: 440102d

[github-actions]

All changed packages have been documented.

• ✅ @typespec/http-client-python

Show changes

@typespec/http-client-python - fix ✏️

Fix serialization regression where @clientDefaultValue defaults on model properties were no longer included in the request body. Defaults are again materialized in the model's data dictionary at construction time so they are sent on the wire, while the attribute-access fallback for unset fields is preserved.