Tests fail if the Python interpreter binary isn't called "python"
Some tests (the tlsfuzzer tests, and tests/suite/multi-ticket-reception.sh
) fail if the Python interpreter binary isn't called python
. That is the case at least on Debian(-ish) systems with only Python 3 installed, where the interpreter is called python3
. Part of this must be fixed in tlsfuzzer (I've already raised an issue there).
For the GnuTLS side of things the proper fix would be to use AM_PATH_PYTHON
in configure.ac
, and use the PYTHON
variable provided by it to call the interpreter.
I'll be happy to prepare a patch, just one question: Is there any reason not to strictly require Python 3? Tlsfuzzer and tlslite-ng both give their requirements as at least Python 3.3 or 2.6. AM_PATH_PYTHON
does not support those as alternatives, so it's either 3.3 (or newer), or no version check.