Well, that's what I believed too, but here's a simple example that
troubles me.
A simple python script, any javascript programmer should be familiar
with:
1) dummycommand.py
import time
def dummy() :
for i in range(0,10) :
print "dummy process", i+1,"/10"
time.sleep(0.2)
if __name__ =='__main__' :
dummy()
>> when you run (>> python dummyscript.py) it, you get this :
dummy process 1 /10
dummy process 2 /10
dummy process 3 /10
dummy process 4 /10
dummy process 5 /10
dummy process 6 /10
dummy process 7 /10
dummy process 8 /10
dummy process 9 /10
dummy process 10 /10
2) Now, the canonical nodejs example from child processes
documentation : test.js
var sys = require('sys'),
spawn = require('child_process').spawn,
dummy = spawn('python', ['/home/test/dummycommand.py']);
dummy.stdout.on('data', function (data) {
sys.print('stdout: ' + data);
});
>> when you run it, you have to wait some while before eventually getting :
stdout: dummy process 1 /10
dummy process 2 /10
dummy process 3 /10
dummy process 4 /10
dummy process 5 /10
dummy process 6 /10
dummy process 7 /10
dummy process 8 /10
dummy process 9 /10
dummy process 10 /10
I think I missed something ?