> My apologies for being a day late, got working on some other things.
> So here's the scoop as it relates to the issue at hand:
Something else I meant to mention: your problem is that the test suite
fails in some circumstances, but these circumstances are not met for most
core developers or when
> My apologies for being a day late, got working on some other things.
> So here's the scoop as it relates to the issue at hand:
>
> - If you run rt.bat from the trunk as-is and place it in a path that
> contains an empty space, you receive the error outlined in
> resultwithspace.txt.
>
> - If you
Mark,
My apologies for being a day late, got working on some other things.
So here's the scoop as it relates to the issue at hand:
- If you run rt.bat from the trunk as-is and place it in a path that
contains an empty space, you receive the error outlined in
resultwithspace.txt.
- If you run
Mark,
Sounds good, I will get patching tonight. Any thoughts on CreateProcessW ?
Joseph Armbruster
On 6/4/07, Mark Hammond <[EMAIL PROTECTED]> wrote:
> All,
>
> I wanted to pass this one around before opening an issue on it.
> When running the unit test for popen via rt.bat (in PCBuild8),
>
> All,
>
> I wanted to pass this one around before opening an issue on it.
> When running the unit test for popen via rt.bat (in PCBuild8),
> I received the following error:
>
> === BEGIN ERROR ===
>
> C:\Documents and
> Settings\joe\Desktop\Development\Python\trunk\PCbuild8>rt test_popen
> Deletin
All,
I wanted to pass this one around before opening an issue on it.
When running the unit test for popen via rt.bat (in PCBuild8),
I received the following error:
=== BEGIN ERROR ===
C:\Documents and
Settings\joe\Desktop\Development\Python\trunk\PCbuild8>rt test_popen
Deleting .pyc/.pyo files
