Wow, glad someone is doing this, looks ideal. We’ve a cargo bike with battery failing (physical connector we can’t replace and some cells borderline), when you get to Yahama motors we’d be interested to look into it.
Is there an intention to bring the auto backend selection to the non-pip interface? I know we can configure this like you show https://docs.astral.sh/uv/guides/integration/pytorch/ but we have folks on different accelerators on Linux and remembering ‘uv sync --extra cu128’ at the right time is fragile so we just make cpu folks have the CUDA overhead too currently.
(As always, big fans of Astral’s tools. We should get on with trying pyx more seriously)
The main NuGet was problematic for a long time e.g. not providing any control over transitive dependencies (like pip at the time). You had to use https://fsprojects.github.io/Paket/ if you wanted safe and consistent resolution. NuGet since got their act together and it’s not as flawed now.
We do something similar with a mix of C++, Fortran, and CUDA dependencies. Using https://cibuildwheel.pypa.io/en/stable/ and the repair functionality to restrict the manylinux to something sensible seems to have handled the complexity - while we mostly use Debian and Ubuntu the Arch folks seemed OK too.
We want to share the wheels more smoothly though and having been looking at pyx for that. Seems promising.
It's definitely possible, and my current company were very happy to agree to 4/5 of the time for 4/5 of the salary and it's working out well for everyone. However, I've also found some organisations - that are otherwise good - to be hostile to working less than full hours. Since we work on interesting problems and they were happy to go with 80% it made it an easy task deciding which job to accept!
I should add that's it's a start-up so some weeks I work more and others less. But I still have the day my kids that I wanted.
Perhaps try quietly asking your current company? They might surprise you and start a trend.
