I'm not sure, but I think it's a problem with the psycopg backend under Python 2.3.5. When I loaded fixtures with Python 2.3.5 I got no errors and the fixtures haven't been loaded. When I loaded fixtures with Python 2.5 I got an error and when I fixed it the fixtures were loaded. I used the same fixtures data. I'm sorry, but I don't have Python 2.3.5 environment anymore, so I can not check it.
Regards, Alex Arshavski. On Jan 17, 12:42 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Jan 16, 2008 10:47 PM, knight <[EMAIL PROTECTED]> wrote: > > > > > I have figured out what theproblemis. > > I was using python 2.3.5. And with this python version, Django says > > that X entities were imported, but none is really imported. > > And after installing python 2.5, I got the error message on missing > > dependencies. > > This is interesting - I wasn't aware of any differences that might > exist with the Python 2.3.5 backend. > > Is this aproblemwith the psycopg backend under Python 2.3.5? Does it > undergo dependency failures in a different way to the Python 2.5 > backend? > > If you run the Django system tests (the runtests.py script in the test > directory of a Django checkout) using Python 2.3.5, do you get any > failures? > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
