Thomas Heller-2 wrote:
>
> Grant Edwards schrieb:
>
> [snip]
>
>>
>> Traceback (most recent call last):
>> File "surfedit.py", line 28, in ?
>> File "Gnuplot\_Gnuplot.pyc", line 178, in __init__
>> File "Gnuplot\gp_win32.pyc", line 117, in __init__
>> File "subprocess.pyc",
On 2007-04-18, Thomas Heller <[EMAIL PROTECTED]> wrote:
> I think this is a subprocess bug. It is often attributed to
> py2exe because usually developers do never run the script in
> pythonW.exe instead of python.exe, and later build a *windows*
> program with py2exe (the *windows* program has no
Grant Edwards schrieb:
> I'm trying to use the py-gnuplot module on windows, and have
> been unable to get it to work reliably under Win2K and WinXP.
>
> By default, it uses popen(gnuplotcmd,'w'), but in some
> situations that consistently gets an "invalid operand" IOError
> when write() is called
On 2007-04-18, Erik Johnson <[EMAIL PROTECTED]> wrote:
>
> "Grant Edwards" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
>
>> How does one troubleshoot errors that happen three layers deep
>> in the subprocess module?
>
> I think the problem is more likely in how your py2exe is
>
"Grant Edwards" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> How does one troubleshoot errors that happen three layers deep
> in the subprocess module?
I think the problem is more likely in how your py2exe is getting
bundled, rather than any real problem with the subprocess
I'm trying to use the py-gnuplot module on windows, and have
been unable to get it to work reliably under Win2K and WinXP.
By default, it uses popen(gnuplotcmd,'w'), but in some
situations that consistently gets an "invalid operand" IOError
when write() is called on the pipe.
So I switched to sub
