Sandy Walsh wrote:
Yes it seems to be a flush problem. Strange how it doesn't require the
explicit flush() when the console window appears, but does otherwise.
Either way, it gives me a good direction to chase after.
[snip]
It buffers for efficiency reasons, but if it can detect that it's
con
Thanks Marco & Al,
Yes it seems to be a flush problem. Strange how it doesn't require the
explicit flush() when the console window appears, but does otherwise.
Either way, it gives me a good direction to chase after.
Thanks again for your quick help guys!
-Sandy
Marco Bizzarri wrote:
You c
Sandy Walsh wrote:
Hi there,
Seeing some really weird behavior and perhaps someone has seen something
similar:
I have a python script that launches as a Windows Scheduled Task. The
program simply opens a disk file and writes some text to it:
---
f = open("waiting.txt", "w")
x = 0
while 1:
You could try to flush the file? Maybe it would flush once you close,
which never happens; did you try to limit the amount of times it run
inside the 'while' loop?
Regards
Marco
On Mon, Oct 26, 2009 at 6:17 PM, Sandy Walsh wrote:
> Hi there,
>
> Seeing some really weird behavior and perhaps so
Do you "import time"?
Sandy Walsh wrote:
Hi there,
Seeing some really weird behavior and perhaps someone has seen something
similar:
I have a python script that launches as a Windows Scheduled Task. The
program simply opens a disk file and writes some text to it:
---
f = open("waiting.txt
Hi there,
Seeing some really weird behavior and perhaps someone has seen something
similar:
I have a python script that launches as a Windows Scheduled Task. The
program simply opens a disk file and writes some text to it:
---
f = open("waiting.txt", "w")
x = 0
while 1:
f.write("Sleeping
