Man, a lot of those sound familiar.  A lot of hard-coded path problems are especially annoying since the official Django documentation often tells you to do it that way.<p>On a semi-related topic - I have an old 0.96 Django app that was using an old database migration framework that isn't supported in the newer versions of Django.  For that framework I wrote the Django migrations in manually generated SQL.  Anyone know how I could update to django-evolution or South with this hand coded SQL and still preserve my existing data?<p>The documentation for django-evolution says:<p>&#62; Django Evolution imposes one important restriction on your development process:  If you intend to make a change to your database, you <i></i>must<i></i> do it through Django Evolution. If you modify the database outside of Django and the Django Evolution framework, you're on your own.<p>Which makes me think I can't use that.