sys.stdout linebuffered

[Thomas Guettler]

Hi,

I start a long running script like this (unix):

nohup foo.py > foo.log &

Now Python thinks sys.stdout should not be
line buffered. How can I force linebuffering?

I want to see the log file while the script is
still running.

I don't like this solution (Wrapping sys.stdout
with an own class)

http://groups.google.de/groups?hl=de...3.fitlinxx.com

The "-u" switch is not an option.

Thomas

[Benjamin Niemann]

> I start a long running script like this (unix):

nohup foo.py > foo.log &

Now Python thinks sys.stdout should not be
line buffered. How can I force linebuffering?

I want to see the log file while the script is
still running.

I don't like this solution (Wrapping sys.stdout
with an own class)

http://groups.google.de/groups?hl=de...3.fitlinxx.com

The "-u" switch is not an option.

Even if you use
#!/usr/bin/python -u
in your script?

[Peter Hansen]

Thomas Guettler wrote:

I start a long running script like this (unix):

nohup foo.py > foo.log & [snip] The "-u" switch is not an option.

That statement is suspect, and like Benjamin I wonder whether
it really is true. Nevertheless, in the unlikely case that you
absolutely cannot use the -u switch, look at the description of
that option in the output of "python -h" and use the environment
variable mentioned there instead.

-Peter

[Thomas Guettler]

Am Wed, 26 May 2004 09:40:01 -0400 schrieb Peter Hansen:

Thomas Guettler wrote:

I start a long running script like this (unix):

nohup foo.py > foo.log & [snip]

The "-u" switch is not an option.

That statement is suspect, and like Benjamin I wonder whether
it really is true.

I like to use #!/usr/bin/env

===> cat minus-u.py
#!/usr/bin/env python -u

===> ./minus-u.py
/usr/bin/env: python -u: No such file or directory
Nevertheless, in the unlikely case that you
absolutely cannot use the -u switch, look at the description of
that option in the output of "python -h" and use the environment
variable mentioned there instead.

The environment variable has the drawback,
that I need to set it before every call to this
script. Other scripts should not be unbuffered.

Thomas

[Peter Hansen]

Thomas Guettler wrote:

I like to use #!/usr/bin/env

===> cat minus-u.py
#!/usr/bin/env python -u

===> ./minus-u.py
/usr/bin/env: python -u: No such file or directory

Consider using /usr/bin/python instead?

Nevertheless, in the unlikely case that you
absolutely cannot use the -u switch, look at the description of
that option in the output of "python -h" and use the environment
variable mentioned there instead.

The environment variable has the drawback,
that I need to set it before every call to this
script. Other scripts should not be unbuffered.

If this is the only script with special needs, why not
just create a separate shell script which invokes python
on the other script directly?

#!/bin/sh
/usr/bin/env python -u specialscript.py
-Peter

[Michael Hudson]

"Thomas Guettler" <gu*****@thomas-guettler.de> writes:

Hi,

I start a long running script like this (unix):

nohup foo.py > foo.log &

Now Python thinks sys.stdout should not be
line buffered. How can I force linebuffering?

I want to see the log file while the script is
still running.

I don't like this solution (Wrapping sys.stdout
with an own class)

http://groups.google.de/groups?hl=de...3.fitlinxx.com

Why? It appears to solve your problem!

Cheers,
mwh

--
I think if we have the choice, I'd rather we didn't explicitly put
flaws in the reST syntax for the sole purpose of not insulting the
almighty. -- /will on the doc-sig