Russell, thanks for the help but I beleive we're talking about a different issue here.
My issue is that if I do something like this >>> g = 5 >>> g 5 It will run the test and print out the 5 while running... ......... 5 .....FF... and then give a Expected: 5 Got Nothing error. So its not that its printing out extra data, its that it's printing out the results when instead it should be returning them..... On Dec 3, 2:37 am, Russell Keith-Magee <[email protected]> wrote: > On Thu, Dec 3, 2009 at 6:29 PM, Dave Fowler <[email protected]> wrote: > > My Django tests have started to print out the results instead of > > registering them for the test results. You can see here, as the tests > > are run it prints out the True and False results (where normally it > > just prints out a list of periods) that the docstring tests are > > expecting, > > > and then latter errors out saying that it got no result. > > It looks to me like you've got a stray print statement somewhere in > your code. Doctests track all content written to stdout, not just the > printed value of the return value of a function. If you have a stray > debug print statement somewhere in your code, it will be corrupting > your results (unless, of course, you update the expected results in > your test to include the debug output). > > Yours, > Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
