On Jan 29, 7:12 pm, Pappy [EMAIL PROTECTED] wrote:
SHORT VERSION:PythonFile B changes sys.stdout to a file so all 'prints' are
written
to the file. Pythonfile A launchespythonfile B with os.popen(./B
2^1 dev/null ). PythonB's output disappears into never-never
land.
LONG VERSION:
I am
On Mon, Jan 29, 2007 at 03:12:37PM -0800, Pappy wrote:
SHORT VERSION:
Python File B changes sys.stdout to a file so all 'prints' are written
to the file. Python file A launches python file B with os.popen(./B
2^1 dev/null ). Python B's output disappears into never-never
land.
LONG
Sadly, the group is tied to Python 2.3 for now.
Actually, I got around this problem by using an intermediate process that
happens to handle output on its own (bsub).
On 1/30/07, Chris Lambacher [EMAIL PROTECTED] wrote:
The subprocess module is probably a good starting point:
On Tue, Jan 30, 2007 at 10:42:22AM -0500, Jason Persampieri wrote:
Sadly, the group is tied to Python 2.3 for now.
Subprocess for 2.2 and 2.3:
http://www.lysator.liu.se/~astrand/popen5/
Win32 installers for subversion for 2.2 and 2.3:
http://www.lysator.liu.se/~astrand/popen5/
-Chris
SHORT VERSION:
Python File B changes sys.stdout to a file so all 'prints' are written
to the file. Python file A launches python file B with os.popen(./B
2^1 dev/null ). Python B's output disappears into never-never
land.
LONG VERSION:
I am working on a site that can kick off large-scale
