It seems you're trying to take a Django application which was written
three releases cycles (or more) ago (since the syntax in some of your
code samples screams out that it's from an app written against 0.90 or
0.91) and attempting to simply fix it piecemeal to run on 1.0.
Speaking from experience, that's not going to work and you're going to
spend several months posting to the list saying, "OK, I got a new
error, now what?"

You've already been given a link to the backwards-incompatible changes
list, which in turn links back to archived lists of changes going all
the way to the oldest versions of Django. Your best bet is to:

1. Work out exactly which version of Django (most likely 0.91) your
application was originally written for.
2. Spend some quality time with the documentation for the Django 1.0
release to thoroughly learn how things work now.
3. Work through the list of changes, one step at a time, until you're on 1.0.

This will be tedious, but fortunately we've been extremely obsessive
about documenting each and every change you'll need to deal with and
how to work through it.


-- 
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

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

Reply via email to