On Wed, Feb 18, 2009 at 9:13 AM, Jim <jim.heffe...@gmail.com> wrote:
[snip]

>
> ----------------------------------------------------------------------------
> Snip of output:
>
>  :
> Running post-sync handlers for application pkgs
> Running post-sync handlers for application tinymce
> Running post-sync handlers for application mptt
> Loading 'initial_data' fixtures...
> Checking '/usr/local/lib/python2.6/site-packages/django/contrib/auth/
> fixtures' for fixtures...
> Trying '/usr/local/lib/python2.6/site-packages/django/contrib/auth/
> fixtures' for initial_data.xml fixture 'initial_data'...
> No xml fixture 'initial_data' in '/usr/local/lib/python2.6/site-
> packages/django/contrib/auth/fixtures'.
> Trying '/usr/local/lib/python2.6/site-packages/django/contrib/auth/
> fixtures' for initial_data.xml.gz fixture 'initial_data'...
> No xml fixture 'initial_data' in '/usr/local/lib/python2.6/site-
> packages/django/contrib/auth/fixtures'.
> Trying '/usr/local/lib/python2.6/site-packages/django/contrib/auth/
> fixtures' for initial_data.xml.zip fixture 'initial_data'...
>  :


This is normal output for verbosity=2 (I think it is more verbose since
support for compressed fixtures was added but I haven't checked in detail).
It's printing out all the places it is looking for initial_data, but there
is no error if it doesn't exist, it just moves on. (There was a time when
the first failure to find an initial data file caused the search to end, but
r9646 fixed that a couple of months ago).

Are you actually encountering an error with having your own initial data
loaded?

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-users@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
-~----------~----~----~----~------~----~------~--~---

Reply via email to