On Sun, Nov 18, 2012 at 10:53 PM, Olemis Lang <ole...@gmail.com> wrote:
> Maybe stdout is redirect somewhere else > That seems likely, andI was hoping someone would know how to deal with this since I'm just running the standard Trac unit tests. > or your messages are > entangled in the tons of prose output by unittest runners , ... No, there is no output at all from print statements. > You > should use the log in functional tests and anywhere you have access to > an environment (<= indeed if that's the case those will be functional > tests already ;) . I don't follow. How does this help me debug a unit test? > If you provide further details the response might be more accurate . > ;) > What further details would you like? I'm not asking for help with debugging a particular unit test, I'm just asking if anyone else has had success directing print statements to the console when running unit tests. I haven't had a chance to try Ethan's suggestions yet, but those look promising. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
