Django 1.4.9 and 1.5.5 released
djangoproject.com
Django 1.4.9 and 1.5.5 released
1–10 of 24 posts
Re: Django 1.4.9 and 1.5.5 released
#2Does the removal of the limit on the password length mean that the DoS is fully mitigated by the password hashing speedup?
Re: Django 1.4.9 and 1.5.5 released
#3How does this impact the release of 1.6, considering that 1.6RC1 was released yesterday? Does 1.6RC1 contain these fixes, or does this mean that 1.6RC2 is coming out soon?
Re: Django 1.4.9 and 1.5.5 released
#4Just curious, how badly would an upgrade from 1.2 go? I want to do it if it takes less than a day.
Re: Django 1.4.9 and 1.5.5 released
#5Just curious, how badly would an upgrade from 1.2 go? I want to do it if it takes less than a day.
Should be reasonably painless. You'll want to read the release notes for 1.3, 1.4, and 1.5, because there are a couple of things that have been deprecated and/or removed. And even a few things that have moved but are otherwise the same. I would think that a day would be sufficient for most peoples' uses of Django. I upgraded from 1.2 to 1.5 a few months ago, and it only took an hour (and this was 10 sites worth of code).
Re: Django 1.4.9 and 1.5.5 released
#6Just curious, how badly would an upgrade from 1.2 go? I want to do it if it takes less than a day.
In my experience it isn't the Django upgrades that go poorly, but all of the other packages that I'm using. A day to upgrade from 1.2 seems reasonable. A day to upgrade the rest of your packages might be significantly more time consuming.
Re: Django 1.4.9 and 1.5.5 released
#7Just curious, how badly would an upgrade from 1.2 go? I want to do it if it takes less than a day.
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 ).
Re: Django 1.4.9 and 1.5.5 released
#8How does this impact the release of 1.6, considering that 1.6RC1 was released yesterday? Does 1.6RC1 contain these fixes, or does this mean that 1.6RC2 is coming out soon?
1.6 will inevitably get the fixes, but as it's not a security release and 1.6 is not officially out yet, they'll probably just bundle them with the actual release.
Re: Django 1.4.9 and 1.5.5 released
#9Just curious, how badly would an upgrade from 1.2 go? I want to do it if it takes less than a day.
Do you have good tests? I've done this pretty recently and it got somewhat messy -- though I had great test coverage on the project that I upgraded, so it probably only took a day or so.
The main road bump I hit was Django Piston. It's totally broken past 1.5 and there are a gazillion forks that solved non-overlapping subsets of the problems I was having.
Re: Django 1.4.9 and 1.5.5 released
#10Just curious, how badly would an upgrade from 1.2 go? I want to do it if it takes less than a day.
I'm curious as well. Did anyone have problems with the new timezone thing that came with 1.4?