[gnutls-devel] GnuTLS | Tests fail if the Python interpreter binary isn't called "python" (#1034)

Development of GNU's TLS library gnutls-devel at lists.gnutls.org
Sun Jun 14 15:20:20 CEST 2020

Airtower created an issue: https://gitlab.com/gnutls/gnutls/-/issues/1034

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](https://github.com/tomato42/tlsfuzzer/issues/670)).

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.

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1034
You're receiving this email because of your account on gitlab.com.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20200614/6ad226da/attachment-0001.html>

More information about the Gnutls-devel mailing list