[pywin32-bugs] [ pywin32-Bugs-935071 ] testall.py fails with space in install path

[SourceForge.net <no...@so...>]

Bugs item #935071, was opened at 2004-04-14 11:14
Message generated for change (Comment added) made by jaraco
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=935071&group_id=78018

Category: win32
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Jason R. Coombs (jaraco)
Assigned to: Nobody/Anonymous (nobody)
Summary: testall.py fails with space in install path

Initial Comment:
When I run testall.py, some of the tests run, but others 
fail opening the file.  It appears to be a bug with the 
install location and the presence of a space.  Below is 
the output of testall on my machine.  After the output 
below, the program hangs.  Note, I have removed all 
non-standard modules from the test folder.  Build is 200 
for Python 2.3.

C:\Program Files\Python\Lib\site-packages\win32
\test>testall
.......................Time zone in effect is Mountain 
Daylight Time
Next timezone change happens at 04/01/00 02:00:00
.............python.exe: can't open file 'C:\Program'
python.exe: can't open file 'C:\Program'
python.exe: can't open file 'C:\Program'
python.exe: can't open file 'C:\Program'
python.exe: can't open file 'C:\Program'


----------------------------------------------------------------------

>Comment By: Jason R. Coombs (jaraco)
Date: 2005-03-13 08:23

Message:
Logged In: YES 
user_id=599869

I apologize for any time you might have wasted on this.  The
problem did indeed exist on that install.  The problem does
not exist on a Python 2.4 install with build 203 of the
win32 extensions.

For that reason, and since no one else has reported this
problem, I suggest the ticket just be closed.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2005-03-04 22:18

Message:
Logged In: YES 
user_id=14198

Can you please try and work out which specific test is
failing here?  I can't see where in the test suite this
could happen.  Just run each .py file in that directory
individually

Thanks

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=935071&group_id=78018