On Thu, Apr 15, 2010 at 3:48 PM, Bill Freeman <ke1g...@gmail.com> wrote:
> Sadly, the problem string doesn't occur at the top level of any of those > local > vars. It was worth a shot. It's probably in the context. > > If I were you, I'd go find the raise wrapped... in debug.py down at the > bottom > of the stack trace, and stick a pdb.set_trace() there. Then (assuming you > do this under manage.py runserver) you can poke around to see what was > being rendered and what's in the context. The exception being wrapped may > have useful information that isn't showing in the stacktrace. If you can > find > the actuall line of code that is getting the exception, you may be > able to figure > out why it thinks it has to convert something to ascii (which is probably > the > default string encoding, use sys.getdefaultencoding() to find out). > Probably > something is applying str() to a unicode object. > > I'm sorry that I can't provide a shortcut. Perhaps someone else will. > If there is a way to run the app using Python 2.5 instead of 2.6 then the debug information would include the original traceback. Alternatively if it could be run with a recent checkout of either the 1.1.X branch or trunk then the full traceback would appearing, instead of it getting cut off at "raise wrapped". 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.
