I started playing around with Django sometime early 2009, did the
tutorial and got started on a toy project. Then something came inbetween
and now, coming back to my toy project I notice that the unit test spit
out a lot of errors relating to the migration tool South. I've haven't
written any test relating to South. My project isn't importing South and
when I remove South from INSTALLED_APPS the errors go away.

So I guess these errors are relating to some testing Django and/or
South does per default and that the errors might be due to some version
incompatibility between the Django/South versions I had installed last
year and the ones that are installed now.

My question isn't really about how to resolve this particular issue but
rather about best practices for maintaining a consistent "Django stack",
so that similar errors will not happen in the future.


Oivvio

-- 
http://pipedreams.polite.se/about/


-- 
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.

Reply via email to