Re: [PATCH] test: use the python interpreter in sh.config

Subject: Re: [PATCH] test: use the python interpreter in sh.config

Date: Tue, 04 Aug 2015 16:35:11 +0200

Cc:

David Bremner <david@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 configure step will fail if it can't find
> it.

pushed.

d

Previous message (by thread): Re: [PATCH] test: use the python interpreter in sh.config

Thread:

David Bremner—Support running test suite using python3 [inbox, unread]
- David Bremner—[PATCH 1/4] test: make python tests compatible with python3 [inbox, notmuch::patch, notmuch::pushed, notmuch::trivial, unread]
- David Bremner—[PATCH 2/4] configure: add ability to force python version via environment [inbox, notmuch::patch, notmuch::pushed, notmuch::trivial, unread]
- David Bremner—[PATCH 3/4] test: use the python interpreter in sh.configure [inbox, notmuch::obsolete, notmuch::patch, unread]
  - David Bremner—Re: [PATCH 3/4] test: use the python interpreter in sh.configure [inbox, unread]
    - David Bremner—[PATCH] test: use the python interpreter in sh.config [inbox, notmuch::patch, notmuch::pushed, unread]
      - Tomi Ollila—Re: [PATCH] test: use the python interpreter in sh.config [inbox, unread]
      - David Bremner—Re: [PATCH] test: use the python interpreter in sh.config [inbox, unread]
- David Bremner—[PATCH 4/4] test: redirect man output to /dev/null [inbox, notmuch::patch, notmuch::pushed, notmuch::trivial, unread]