> It may take a couple more days to work this out. It's only been 48 hours > since you posted the original problem and less than 24 hours since you > posted a portion of your code that causes the problem. It is very > unusual behaviour for Django; the templating code is normally very fast, > but this isn't a trivial thing to work out. > > Anybody working on this problem (including me), has to work up the > necessary wrapper code to try and replicate the problem and create some > test data and hope we see the same thing. If we don't, we have to bounce > it back to you to get some more information. So understand that this can
I'm sorry if I offended anyone by my post about trying another template engine. I certainly wasn't expecting that anyone was going to spend a whole lot of time trying to figure out if I was doing something wrong, or if there was some kind of Django issue. My original post was to really geared to finding any resources that might give some best-practice guidelines Barring that, I was really only hoping for any quick or easy suggestions others may have. Since no quick suggestions were forthcoming (I still have to look into the issue mentioned by Karen Tracey) I was going to simply move on to find the best solution for me. Now that I'm aware that others are actually trying to reproduce my problem, I'll stick with it for now and also try and do some more digging on my own. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
