On Tuesday 09 May 2017 06:00:31 rmschne wrote: > > I'm sorry - but this isn't your real error. > > > > You will see it in your WSGI daemon logs once you set DEBUG to > > false. > > > > > > > > This error is caused by Django trying to print the error using ascii > > codec for the debug output (I haven't chased it down any further > > and I should really report it). > > > > > > > > As said, your real error is somewhere else and that will probably > > make more sense. > > > > > > > > > > Melvyn Sopacua > > Melvyn, > > Thanks. I understand what you are saying. Obvious, but I didn't notice > that. However, I do think it's a Django bug. This app is not running > on a web server so there is no WSGI daemon.
Ah yes! That triggers a memory. Since `python manage.py runserver` runs on terminal the codec is set to ascii (even when using a UTF-8 locale). So set debug to false and see what comes up in the console. Another way is to temporarily change the data to ascii. It should then still yield an error and that is your real one. > Do you have a suggestion > on what I can do to get a better detection of the error to enable > reporting it? Since runserver crashes, your options are limited. You could maybe construct a test case using django.test.Client[1] and see what is triggered. -- Melvyn Sopacua -------- [1] https://docs.djangoproject.com/en/1.11/topics/testing/tools/#the-test-client -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2030225.42xNKJQA4H%40devstation. For more options, visit https://groups.google.com/d/optout.
