Comments on: Most Important Changes in Django 1.5

By: Suhail Vs

Suhail Vs — Fri, 10 May 2013 06:19:00 +0000

so auth_profile_module is going to depreciate. that sounds bad. any way i hopes the new customizable user will be great.

By: silent1mezzo

silent1mezzo — Mon, 31 Dec 2012 15:59:00 +0000

I always wait until Django has released the final version until I upgrade my proudction systems. I would wait until 1.5 is officially released to upgrade. If you’re using virtualenv’s and pip it’s fairly simple to upgrade.

Because there’s very little backwards incompatibility I wouldn’t worry to much about upgrading.

By: Aidan Zhakypov

Aidan Zhakypov — Sat, 29 Dec 2012 06:48:00 +0000

If you had to develop a new (production) web site now, would you use Django 1.5?

By: Derek

Derek — Mon, 03 Dec 2012 10:12:09 +0000

Any ideas as to date for Djnago 1.5 … early in 2013?

By: Kerr

Kerr — Sat, 01 Dec 2012 16:52:09 +0000

I didn’t know about the multi-column indexes feature. For me, this is almost as welcome as the configurable user model enhancement.

By: Adam McKerlie

Adam McKerlie — Thu, 29 Nov 2012 14:29:57 +0000

The reason why I didn't include the new URL style is that it's just a deprecation that was already announced in 1.3. For those that don't know you'll now need to do your URLs as {% url "myview" %} if you want to use the literal string or {% url variable_name %} if you want to pass in a variable. This just continues on with the consistency of variables and strings in Django's templates.

By: Kern3l

Kern3l — Thu, 29 Nov 2012 14:22:58 +0000

Is “New URL” change so obvious that it needed no comment? ;]

By: Adam McKerlie

Adam McKerlie — Thu, 29 Nov 2012 12:42:13 +0000

You are most definitely correct. Updated!

By: David

David — Thu, 29 Nov 2012 08:41:45 +0000

Think you mean 404.html