I looked a bit deeper into this issue, and so far I can say, that the
exception is raised by django.test.TestCase in the method _pre_setup.
call_command('flush', verbosity=0, interactive=False) is where it
originates. Calling ./manage.py flush on the command line works like a
charm. I also have to note, that DocumentTests includes 3 tests - the first
always works while the later two always fail. But it is not depend on the
test itself, but simply on the order of the tests in the test case.Bye, Oliver -- Oliver Andrich <[EMAIL PROTECTED]> --- http://oliverandrich.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
