> Quoting from the book of "if you hear hoofbeats, think horses, not > zebras": This obviously isn't normal Django behaviour and since calling > views is easily the most common operation in Django, it's safe to assume > that any breakage here in Django would have been noticed by other > people. Which means the problem is almost certainly in your code. None > of which you have shown us and we can't guess what it might contain.
Oh, I'm fully expecting that it's something that I'm doing, didn't mean to imply it was a Django issue. I was hoping that it was an obvious enough screw up though. I'm attaching a tarball, which immitates my setup in a minimal fashion. At least when running on my system, the following browser request triggers this behavior: http://servername/test/ > rendering at all. You could try printing things like the output of > traceback.print_stack() in your view to see if it's called the same way > both times, for example. I didn't see any differences in the two outputs. > shortest possible example more or less naturally reveals what the > problem is in the first place, because you end up seeing which line is > critical to triggering the issue at hand. Unfortunately, it didn't work here - I've got a view that only calls a template, and a template which is almost completely empty. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
blarg.tgz
Description: Binary data
