Charles-François Natali added the comment: It's not an issue at all, it's simply buffering in effect. Depending on the version, stdout/stderr is either unbuffured or fully buffered, see http://bugs.python.org/issue13597
Simply pass '-u' and streams will be unbuffered, and appear in the order in chich the print() calls are made. ---------- nosy: +neologix resolution: -> invalid stage: -> committed/rejected status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16689> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
