On Tue, Apr 13, 2010 at 2:14 AM, Phlip <phlip2...@gmail.com> wrote: >> How do I access the error message? > > In this case, turning on --verbosity=2 reveals a huge dump, and > tweezering through it reveals the fixture file was not found. (A > colleague bumped its app from the app list.) > > It seems that "fixture not found" should be a fatal error, not a > silent warning. The fixtures= line also has this bug.
Django 1.2 addresses this; the default verbosity for the "no fixtures found" message has been decreased, so you should see the message at the default verbosity. This change hasn't been backported back to 1.1 because it's not strictly a bug. Yours, Russ Magee %-) > -- > Phlip > > -- > 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. > > -- 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.
