On 11/19/12, RjOllos <ry...@physiosonics.com> wrote: > When I put `print` statements inside a unit test case I don't see any > output in the console window. Any idea of why this might be? >
Maybe stdout is redirect somewhere else , or your messages are entangled in the tons of prose output by unittest runners , ... 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 know it's not the most elegant way to debug, but sometimes the quickest > way to get some info about a variable when debugging some Trac code, > particularly since I'm still a beginning with python and not proficient > with pdb and other tools that exist. > If you provide further details the response might be more accurate . ;) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- 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.
