Please revert switch to `uv` or provide a fallback, non-rusty backend

[barracuda156]

uv requires rust and thus is broken on systems where rustc is broken. This is a simple package, it can use a normal pure-python build backend.

[barracuda156]

Breakage introduced by 325d7c0

[rec]

Thanks! I'm heading out, but I'll take a look at this shortly.

A quick question: does this break things for people wanting to develop for this library, or users of this library?

I had the impression that end users didn't need uv or poetry to install.

Another question: I never stopped to think about this at all, of course rust is not available on some systems! - do you have a list or something?

Another question: does this mean I have to give up using uv myself for these projects? That would be a bit painful now.

[barracuda156]

I had the impression that end users didn't need uv or poetry to install.

Perhaps not if they install pre-built package via pypi, but they do need a build backend when building from source (which is what MacPorts, FreshPorts, OpenBSD or pkgsrc do). And while all these distributions allow installing their pre-built packages, those won’t build as long as the build backend does not exist for a given architecture/platform.

Another question: I never stopped to think about this at all, of course rust is not available on some systems! - do you have a list or something?

Rust won’t work wherever a recent enough LLVM does not. Those will be niche platforms (*BSDs support a lot of obscure and legacy ones; MacPorts supports macOS versions back to 10.5, and there is no Rust on old ones) and resource-constrained systems (say, I have no idea if LLVM and Rust can built in principle on a low-end RISCV board, but I doubt anyone will be happy to need to bootstrap those just to install a pure-Python package).

Another question: does this mean I have to give up using uv myself for these projects?

This should not have any impact, I believe.

[rec]

Back!

The diff of the commit in question is fairly large, it's not clear how to reconcile the old and new versions.

So what is the simplest way to resolve this issue? Do I just need to add the right backends, and if so, how is this done?

Once I know, I'll write something to apply this to all my repositories, not just this one.

[barracuda156]

I think the only relevant file is https://github.com/rec/xmod/blob/main/pyproject.toml – however I am not sure if there is a way to set build backend conditionally. If not and it is desirable to keep default one as uv, it will work to supply an alternative pyproject-poetry.toml, so that distributions or users can just replace the default one with this, and build everything with poetry.

[rec]

So I think I have a solution: can you test: #10

?

This took longer than I expected. The key idea was the hatchling backend.