[PATCH 1/2] configure: add check for python interepreter name

2015-01-04 Thread David Bremner
David Bremner writes: > Currently we hardcode "python" in several places. This makes things > hard for people who have only commands called python3 and/or > python2. We also add the name to sh.config to eventually replace the > current workaround in the test suite. Pushed, with Tomi's suggested

Re: [PATCH 1/2] configure: add check for python interepreter name

2015-01-04 Thread David Bremner
David Bremner da...@tethera.net writes: Currently we hardcode python in several places. This makes things hard for people who have only commands called python3 and/or python2. We also add the name to sh.config to eventually replace the current workaround in the test suite. Pushed, with

[PATCH 1/2] configure: add check for python interepreter name

2015-01-03 Thread David Bremner
Currently we hardcode "python" in several places. This makes things hard for people who have only commands called python3 and/or python2. We also add the name to sh.config to eventually replace the current workaround in the test suite. --- configure | 26 ++ 1 file

[PATCH 1/2] configure: add check for python interepreter name

2015-01-03 Thread David Bremner
Currently we hardcode python in several places. This makes things hard for people who have only commands called python3 and/or python2. We also add the name to sh.config to eventually replace the current workaround in the test suite. --- configure | 26 ++ 1 file changed,