Django Update - 2014-05-04 to 2014-05-17

Posted by Curtis Maloney on May 18, 2014


I think I missed an entry... sorry, I was on holidays!


A security update, and a bug fix to go with it. Does anyone else think we can do away with view functions to reverse() now?

Don't forget to read over all the security notices to ensure you're doing the right things.

Ticket Movement

Short lived tickets: 54

Tickets Created: 18

Open tickets: 1380 (-23)


How would you like to be able to build more complex expressions in annotations? Does the idea of being able to write:

.annotate(Sum(F('field')+F('otherfield')) / Count('field'))

excite you? Or how about using arbitrary SQL functions:

.annotate(actual=Func('coalesce', F('name'), F('description'), Value("meh")))

Well, Josh Smeaton (jarshwah) has been doing the work on Ticket #14030, and, as I understand it, it's close to ready.

For code that's violated the privacy of the ORM, there's been some talk about a backward compatible parallel path, but nothing's been decided as yet.

Did you know?

The people from Lincoln Loop are wanting to write a book on high performance Django, and have started a Kickstarter campaign. Let's show them how much we like the idea!


I know we're all hanging out for Django 1.7. Unfortunately, security reports always take precedence.

-- Have a better one!

Back to Top