Re: python nproc vs MAKE_JOBS issues

[Greg Troxel <gdt%lexort.com@localhost>]

Thomas Klausner <wiz%gatalith.at@localhost> writes:

> On Mon, Nov 11, 2024 at 11:57:11AM +0000, Jonathan Perkin wrote:
>> I've seen a few similar things to this recently where python modules are
>> being built with complete disregard to MAKE_JOBS, and instead are just
>> spawning a thread for each CPU they find.  For example:
>
> This seems to be py-maturin's default, to use one job per CPU.
>
>> Do any python folks know what is causing this and are able to fix it?
>
> Try the attached patch. Similar patches would need to be applied to
> all users of py-maturin.

Maybe we should simply fix the default in py-maturin, once.  This is a
philosophical disagreement about whether a tool should consume all CPU
resources by default, or by default use one, and take a -j flag.  go is
similarly troubled.

In genearl, I see these issues as bugs in the thinking of ecosystems,
basically that they are the only or most important thing, vs expecting
to interact reasonably with the rest of the world.