Comment #3 on issue 1505 by pekka.klarck: Logging callable that returns
non-string corrupts output file
http://code.google.com/p/robotframework/issues/detail?id=1505
An alternative solution is disabling the callable message support in public
APIs. It needs to be exposed to internals to support lazy trace level
logging, though. This would require a quite a bit less documentation and
testing work than officially supporting callable messages and handling
errors when they are used by accident or incorrectly.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
