Mark,<br><br>Sounds good, I will get patching tonight. Any thoughts on CreateProcessW ?<br><br>Joseph Armbruster<br><br><div><span class="gmail_quote">On 6/4/07, <b class="gmail_sendername">Mark Hammond</b> <<a href="mailto:mhammond@skippinet.com.au">
mhammond@skippinet.com.au</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> All,<br>><br>> I wanted to pass this one around before opening an issue on it.
<br>> When running the unit test for popen via rt.bat (in PCBuild8),<br>> I received the following error:<br>><br>> === BEGIN ERROR ===<br>><br>> C:\Documents and<br>> Settings\joe\Desktop\Development\Python\trunk\PCbuild8>rt test_popen
<br>> Deleting .pyc/.pyo files ...<br>> 43 .pyc deleted, 0 .pyo deleted<br>><br>> C:\Documents and<br>> Settings\joe\Desktop\Development\Python\trunk\PCbuild8>win32Re<br>> lease\python.exe -E -tt ../lib/test/regrtest.py test_popen
<br>> test_popen<br>> test test_popen failed -- Traceback (most recent call last):<br>> File "C:\Documents and Settings\joe\Desktop\Development\Python\...<br><br>I can't reproduce this. I expect you will find it is due to the space in
<br>the filename of your Python directory, via cmd.exe's documented behaviour<br>with quote characters. A patch that allows the test suite to work in such<br>an environment would be welcome, but I think you might end up needing access
<br>to GetShortPathName() rather than CreateProcess().<br><br>Cheers,<br><br>Mark<br><br></blockquote></div><br>