Once in my careerer I was already tasked with stripping a C project from a Python based building system (SCons, IIRC)  because it was damn slow, buggy, and problems with Python and SCons were more severe than with a C codebase itself. I replaced it with kbuild, and it still works nicely in production even today.<p>I&#x27;m hesitant getting anything Python-related next to my C codebase, and IMO, C-people are generally not very enthusiastic about Python. Once the time comes, that something custom needs to be done in the building system, dealing with Python syntax, completely new abstractions, etc. is just more pain than using established solutions that everyone are familiar with (make, autotools, CMake).<p>Maybe Python 3 ecosystem (things like packaging etc.) does not suck as much as Python 2 (though I&#x27;d bet it still does), and maybe Meson is really great, but on top of my Python-implementation reservations, I also don&#x27;t see much of a point: the billions of C legacy code will not be ported to a new building system, a there should be not that much new projects in raw C anyway, with languages like Go, Rust, D showing clear road ahead, baking their own solutions for common building system issues. Projects like &quot;tup&quot; have much more appeal to my C-developer nature, but then again, I didn&#x27;t have opportunity to employ tup anywhere, as nowadays I write every new project in Rust.<p>Than again, it&#x27;s just my personal opinion, and I guess somewhere, some people could find it really fitting their needs.