3 ms·
I've never actually done a 1.2.x to 1.5.x upgrade in one go, but have done plenty of 1.3 to 1.5s. As far as I recall, for Django itself, the 1.2 to 1.3, and 1.
by kingrolo 13y ago
I've never actually done a 1.2.x to 1.5.x upgrade in one go, but have done plenty of 1.3 to 1.5s.
As far as I recall, for Django itself, the 1.2 to 1.3, and 1.3 to 1.4 upgrades were pretty painless, but then 1.4 to 1.5 will involve some work if you make use of function based generic views, as that's when they were removed.
Worth looking at whether your third party apps are still maintained with the new versions as well, as you'll likely be on ancient versions of lots of them if you're using 1.2 (and some may even be obsolete). pip-tools is handy for this ( https://github.com/nvie/pip-tools https://github.com/nvie/pip-tools ).
- thraxil 13y agoI actually found the 1.3 to 1.4 upgrade to be much more work than 1.4 to 1.5. But that was because I'd been using the old style directory layout, so the whole project structure had to change. And I never used function based generic views very heavily, so that didn't factor in very much.
- andybak 13y agoI'm still using the directory layout from 0.96 with Django 1.6. What forced you to change?
- michaelmior 13y agoInteresting. I found the 1.3 to 1.4 upgrade only took a few hours. The 1.4 to 1.5 was a bigger deal because of the new syntax for the {% url %} template tag. Especially since this had to be dealt with in third-party packages.
- erichurkman 13y agoAnd for anyone planning on going up in version, you can start getting ready with {% load url from future %} to get the new syntax (URL names have to be quoted strings).