On Wed, 18 Jul 2018 at 11:56, David Malcolm wrote: > Python 2.6 onwards is broadly compatible with Python 3.*. and is about > to be 10 years old. (IIRC it was the system python implementation in > RHEL 6).
It is indeed. Without some regular testing with Python 2.6 it could be easy to introduce code that doesn't actually work on that old version. I did that recently, see PR 86112. This isn't an objection to using Python (I like it, and anyway I don't touch the parts of GCC that you're talking about using it for). Just a caution that trying to restrict yourself to a portable subset isn't always easy for casual users of a language (also a problem with C++98 vs C++11 vs C++14 as I'm sure many GCC devs are aware).
