Issue 2381: test_subprocess fails if your sys.executable is on a path with a space in it (original) (raw)

Issue2381

Created on 2008-03-18 04:19 by lanny, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg63883 - (view)	Author: Alan Brooks (lanny)	Date: 2008-03-18 04:19
Patch attached that escapes the executable name so this test doesn't fail.
msg63956 - (view)	Author: Ralf Schmitt (schmir)	Date: 2008-03-18 18:02
I can confirm this issue. 2 tests fail without this patch. please apply. here are the failing tests: ====================================================================== FAIL: test_args_string (test.test_subprocess.ProcessTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ralf/tt tt/trunk/Lib/test/test_subprocess.py", line 544, in test_args_string self.assertEqual(p.returncode, 47) AssertionError: 126 != 47 ====================================================================== FAIL: test_call_string (test.test_subprocess.ProcessTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ralf/tt tt/trunk/Lib/test/test_subprocess.py", line 585, in test_call_string self.assertEqual(rc, 47) AssertionError: 126 != 47
msg64120 - (view)	Author: Jeff Balogh (jeff.balogh) *	Date: 2008-03-19 23:12
The patch works for me, and doesn't change anything except the test strings. Not having spaces in your path also helps. ;)
msg66985 - (view)	Author: Gregory P. Smith (gregory.p.smith) *	Date: 2008-05-17 07:17
fixed in trunk r63405