Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/42321 )
Change subject: util/exynos: Port *_cksum.py to python3 ......................................................................
Patch Set 4:
Leave it with `python`, as it’s compatible with both?
No, we should explicitly specify the version to create reproducible behavior (and that should be the version that we are shipping with the coreboot-sdk)
Do we ship Python with the SDK? Because I don't think we do, right?
Python has this sort of weird state in the coreboot build system where it's really "banned" because people don't want it as a dependency (for issues like these, for example), but individual platforms can still choose to use it (because vendors often have Python build tools already and nobody wants to rewrite it all in C). But I don't think we have an officially supported version or anything. (We don't have an officially supported HOSTCC either, after all... we're trying to just vaguely support what most people have and hope that the compiler for build tools shouldn't have an effect on the final firmware binary, which it shouldn't unless we write really bad code.)
So maybe for simple stuff that both Python 2 and 3 should be able to run (which I think should be true for most of what we have... I think the Python guys intentionally tried to backport the most stuff that needs to be changed for Python 3 to Python 2), Paul is right and we should leave the version unspecified to give it the best chance that it will run on either?