On Jan 9, 2009, at 16:53 , Tom wrote:
>
> import sys
> sys.stdout.flush()
>
> was the solution!
>
> Thanks William!
If this solves the problem, it sounds like a bug to me.
Unless Sage is getting killed because of some error condition, the
output should "drain" before the process terminates.
import sys
sys.stdout.flush()
was the solution!
Thanks William!
-Tom
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options
On Fri, Jan 9, 2009 at 4:27 PM, Tom wrote:
>
>
> I think I may have found the source of the error, but not a
> solution. Does Sage (or Python or unix) only save the output to disk
> in chunks of 32Kb? By putting some simple print statements in my
> program, I do see the output being recorded i
I think I may have found the source of the error, but not a
solution. Does Sage (or Python or unix) only save the output to disk
in chunks of 32Kb? By putting some simple print statements in my
program, I do see the output being recorded in the file. I find that
the size of the results file
On Jan 9, 1:53 pm, Tom wrote:
> I'm having difficulty running Sage in the background on a Mac with OSX.
> 5 and getting the output saved in a file. I tried a few permutations
> with different results so I expect I'm making a silly error. Here's
> what I've seen.
> Since the program runs fine i
