Patrick Steinhardt wrote: > The tests in t9835 and t9836 verify that git-b4(1) works with both > Python 2 and 3, respectively. To determine whether we have those Python > versions in the first place we create a wrapper script that directly > executes the git-b4(1) script with `python2` or `python3` binaries. We > then condition the execution of tests on whether that wrapper script can > be executed successfully. s/b4/p4/ in the commit subject and message. You did make me wonder if someone had added some sort of b4 integration into git though. :) Tangentially, with Python 2 having gone EOL upstream in January 2022¹, how long does it make sense to keep supporting it? Debian Bullseye² and RHEL 8³ both have python 3.9. Are there systems in our targeted support matrix which do _not_ have python3? It's not something to fix for this patch, but perhaps if we no longer feel obligated to support python2, someone may choose to remove it from the code and simplify it a bit. ¹ https://www.python.org/doc/sunset-python-2/ ² https://packages.debian.org/search?keywords=python3 (even buster, AKA old, old stable has python 3.7) ³ https://git.rockylinux.org/staging/src-rhel/rpms/python39 (RHEL makes finding a decent URL a pain) -- Todd
