David Bremner writes:
> The configure script chooses "python" if both python and python{2,3}
> exist exists, so this could change the version of python used to run
> the test suite.
>
> The checking for ${NOTMUCH_PYTHON} in the test suite is arguably
> over-engineering, since the configure step
David Bremner da...@tethera.net writes:
The configure script chooses python if both python and python{2,3}
exist exists, so this could change the version of python used to run
the test suite.
The checking for ${NOTMUCH_PYTHON} in the test suite is arguably
over-engineering, since the
On Sun, Aug 02 2015, David Bremner wrote:
> The configure script chooses "python" if both python and python{2,3}
> exist exists, so this could change the version of python used to run
> the test suite.
LGTM. tests pass.
>
> The checking for ${NOTMUCH_PYTHON} in the test suite is arguably
>
The configure script chooses "python" if both python and python{2,3}
exist exists, so this could change the version of python used to run
the test suite.
The checking for ${NOTMUCH_PYTHON} in the test suite is arguably
over-engineering, since the configure step will fail if it can't find
it.
---
The configure script chooses python if both python and python{2,3}
exist exists, so this could change the version of python used to run
the test suite.
The checking for ${NOTMUCH_PYTHON} in the test suite is arguably
over-engineering, since the configure step will fail if it can't find
it.
---
On Sun, Aug 02 2015, David Bremner da...@tethera.net wrote:
The configure script chooses python if both python and python{2,3}
exist exists, so this could change the version of python used to run
the test suite.
LGTM. tests pass.
The checking for ${NOTMUCH_PYTHON} in the test suite is