Reputation: 43
I've a project on Django that needs an upgradation. Should I proceed by making a new project on 1.6 and shifting one by one from Django 1.3 to 1.6 or there's some other easy method?
Upvotes: 3
Views: 1379
Reputation: 18427
What the documentation recommends, do it in steps
-Wall
command to unsilence warningsA more personal note:
From my experience, I also recommend you go to the release notes, go one version after the other, and scan the major changes. While some things are still supported, and will work for you, it doesn't mean that one of the newer version didn't present a better method to do the same thing.
One good example would be the render
. It was presented as an alternative to render_to_response
back in version 1.3, but it didn't catch on that fast. The render_to_response
is still supported, and there isn't any deprecation coming. But it's still good habit to get with the times.
Another personal suggestion - recreate the apps with the new django version, and then copy the files. That's because the new versions use different templating for their settings.py and other files, and it might immediatly highlight to you some of the changes that were brought (such as ALLOWED_HOSTS which was presented in 1.5).
Good luck! Hope it wouldn't be too painful
p.s. - consider waiting a little while longer - Django 1.7 is coming soon, and it's expected to be the biggest release since Django 1.0. Though, on the other hand, upgrading from 1.6 to 1.7 will probably be easier than upgrading from 1.3 to 1.7. I'm not sure what's the best course here, but consider it.
Upvotes: 9