My question on the file object was a shot in the dark based on the only thing that looked odd to me, given that the traceback information was useless. So, if that seems to be correct per the docs, then I think you'll need to get the traceback from the actual error in order to make progress. >From my original note:
To see the traceback associated with the real error try setting DEBUG=True in your test settings file (I assume that works when running under the test framework? If not you'll need a 500.html that Django can find and the proper other settings to have the real root cause traceback emailed to you). Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
