-
Jehan authored
Do not set the interpreter to `python2` but to whatever was found by the AM_PATH_PYTHON2() m4 macro. It looks like the Python2 binary we ship in our DMG may be call "python" only (without the '2'). Let's just make our code more resilient to various builds. I am not sure yet this is the only/actual problem for this issue on macOS, but this is at least in the right way. (cherry picked from commit 8f21c948)
de11e353