IMO, any codebase is significantly easier and safer to maintain if there are tests.
Since we kinda-sorta support SPARK in our toolchain (not for the host though at this time), maybe we should evaluate doing a rewrite in SPARK then: Formal verification beats spot tests which may or may not cover the troublesome situations. ;-)
(What I mean is that it's always possible to up the ante, not that we should actually do that. I'd rather get rid of the kconfig language, and even that idea has dubious value in this context.)
As for the idea of a Python 4 you seem to have here (or if it does come, repeating the massive language differences we had between 2 and 3), it's unlikely to happen. Guido says that a "Python 4" at the scale Python 3 was is
unlikely to happen.
If Python 3->4 is only half as painful as 2->3, this would still be true - and still mean misery for 5+ years. No thanks.
Patrick
--
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado