Carl Sorensen <c_soren...@byu.edu> writes: > On 3/15/20, 8:39 AM, "lilypond-devel on behalf of Han-Wen Nienhuys" > <lilypond-devel-bounces+c_sorensen=byu....@gnu.org on behalf of > hanw...@gmail.com> wrote: > > On Sun, Mar 15, 2020 at 12:05 PM <jonas.hahnf...@gmail.com> wrote: > > > > > > What I'm not really happy with is replacing all of this with custom > > Python scripts, however small they are. Skimming over scan-mf-deps.py, > > that looks totally doable in around half the lines with a sh script. > > What's the motivation to use Python for all of this? > > What's the motivation to use sh for all this? > > You can certainly make it shorter with shell, but will it be > significantly simpler, easier to understand or easier to maintain? > > I decided for Python in this case, because recursion seems like > something I don't want to do in a sh script. > > Personally, I'm totally in favor of using python for creating ninja > files. We have a well-documented, well-maintained, powerful language. > No different flavors (bash, sh, dash, csh, ksh...).
Regarding the "no different flavors" mantra, you might want to speak with the people who were (and still are) involved with the Python2 to Python3 porting effort. -- David Kastrup
