Comment #9 on issue 456 by [email protected]: When logging messages
through stdout timestamps are not accurate
http://code.google.com/p/robotframework/issues/detail?id=456
To follow up from discussion in issue 455...
I think requiring the timestamp, while certainly easy enough, is solving
the wrong issue. In keyword code, I can't see preferring to use a print
with the time string vs the newly enabled logging methods (either robot or
standard). But any external code (not written for or depending on robot)
writing to stdout/stderr is not going to have embedded time and the result
logged messages will be out of sequence and grouped together at the end
after all robot or python logging entries.
