2010/4/5 Tomasz Zieliński <tomasz.zielin...@pyconsultant.eu> > that 'raise wrapped' line is placed in catch-all handler, which > means that > probably some of your code called during template rendering is > broken, > Django catches it and re-raises as TemplateSyntaxError which, > unfortunately, > is vague about ther real problem. >
Prior to Python 2.6, the end of the traceback for the error (the part that would have revealed here that it was a model's __unicode__ method which caused the exception) was included as the "Original Traceback" as part of the exception's message. A change in Python made that original traceback part of the exception value disappear with Python 2.6. This has been fixed in trunk and the 1.1.X branch by including the full traceback in the traceback part of the debug page, so this unfortunate loss of debug information when running under Python 2.6 will be fixed with Django 1.1.2 and 1.2. Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
