Re: [PATCH] t/lib-cvs: cvsimport no longer works without Python >= 2.7

2013-01-13 Thread John Keeping
On Sat, Jan 12, 2013 at 04:27:36PM +0100, Michael Haggerty wrote: >> Even if we were to rip out the fallback code that uses the 2.7-only >> subprocess.check_output() on "cvsps -V", the function is also used >> for doing the real work interacting with cvsps-3.x, so I think this >> patch will be

Re: [PATCH] t/lib-cvs: cvsimport no longer works without Python >= 2.7

2013-01-12 Thread Michael Haggerty
I have the feeling I'm only seeing one side of this conversation... On 01/12/2013 09:40 AM, Junio C Hamano wrote: > The new cvsimport requires at least Python 2.7 to work; do not fail > the cvsimport tests on platforms without one. > > Signed-off-by: Junio C Hamano > --- > > Junio C Hamano wr

[PATCH] t/lib-cvs: cvsimport no longer works without Python >= 2.7

2013-01-12 Thread Junio C Hamano
The new cvsimport requires at least Python 2.7 to work; do not fail the cvsimport tests on platforms without one. Signed-off-by: Junio C Hamano --- Junio C Hamano writes: > http://docs.python.org/2/library/subprocess.html tells me that > check_output has first become available in 2.7. > >