Bernhard Voelker wrote: > The shell seems have to been more safe in that regard.
But the concepts of the shell are stuck in the 40-years-ago past. That's why it is not recommendable as a programming language for real programs [1]. > I'd guess most hosts have python installed nowadays ... the question is > rather which version of it, and how compatible it is: > now it's <3.7 which is incompatible (according to your mail), > but in future there might come more incompatibilities with newer versions. Good point. Yes, Python occasionally (rarely?) makes incompatible changes. So, I've now created a continuous integration at [2]. If a Python release is made that breaks gnulib-tool, this CI will notify me shortly afterwards, and we will have time to adapt gnulib-tool, even before the new Python release lands in the various distros. Bruno [1] https://lists.gnu.org/archive/html/bug-gnulib/2024-03/msg00160.html [2] https://gitlab.com/gnulib/gnulib-tool-ci
