Switch to uv-based management of our python build+test environment

[jleibs]

What

Using our pixi environment for working with the rerun-sdk itself has led to all manner of pain. In theory pixi-build may fix this some day, but it's still not optimized for an explicit maturin develop dev flow.

We move the entire "rerun-sdk" test-oriented environment over to uv, removing all examples and dedicated py-related environments from pixi.

Notable Changes

Building and running python code

BEFORE:

pixi run py-build
pixi run -e py ./my_script.py

NOW:

pixi run py-build

# Run through pixi if you don't have uv
pixi run uv ./my_script.py

# Or just use uv directly if you have it installed
uv run ./my_script.py

[github-actions]

Web viewer built successfully.

Result	Commit	Link	Manifest
✅	1e3a7a2	https://rerun.io/viewer/pr/12176	+nightly +main

View image diff on kitdiff.

^{Note: This comment is updated whenever you push a commit.}

[github-actions]

Latest documentation preview deployed successfully.

Result	Commit	Link
✅	1e3a7a2	https://landing-5203ymanf-rerun.vercel.app/docs

^{Note: This comment is updated whenever you push a commit.}

[jleibs]

@rerun-bot full-check

[github-actions]

Started a full build: https://github.com/rerun-io/rerun/actions/runs/20175669647

[ntjohnson1]

Generally LGTM but I'm lacking enough sleep to think about this holistically.

[ntjohnson1]

This selective inexact usage feels a little footgunny/susceptible to bit rot. I guess if we miss an inexact somewhere then rerun won't be in the environment and we hopefully fail early.

[ntjohnson1]

Fast just allows skipping the JavaScript pieces?

[ntjohnson1]

I think this is overly strict. Did you try bumping the version and seeing if this barfs? For instance if we're on 0.27 then go to 0.28 we'd have duplicate wheels in our wheels dir but unique by version

[jleibs]

Historically this has only been used in CI where there will be a single wheel and the main purpose of this was to avoid needing to pick up a dependency on the version. This is a direct port of the other pixi-oriented version of the same script. I'm going to leave it for now but flag it as a thing I clean up in the pending script cleanup.

[timsaucer]

Something I ran into that I suspect others who frequently use uv/maturin will also is that I cannot just source .venv/bin/activate and then do maturin develop --uv from the rerun_py directory. I have to pass in that additional RERUN_MATURIN_BUILD environment variable and also run the fix_rerun_pth.py. I see that the pixi run py-build command will do those for me, but that means that even though I have this uv environment I can't just use it after setting up. I still need to go through pixi.

Maybe it's worth another look at the fix_rerun_pth.py. I don't have to do this in datafusion-python. There running maturin develop --uv just works.

So I guess what I'm finding is that this does work similar to what I had before except that there is a uv environment but it doesn't work like I would expect it to. I'll keep playing around with it on my flight.

[jleibs]

We are going to hold off merging this until after 0.28 has been released to avoid debugging release-scripts during the release.