Feed Sign in with OpenID OpenID

Simon Willison’s Weblog

Django 1.2 planned features. The votes are in and the plan for Django 1.2 has taken shape—features are split in to high, medium and low priority. There’s some really exciting stuff in there—outside of the things I’ve already talked about, I’m particularly excited about multidb, Model.objects.raw(SQL), the smarter {% if %} tag and class-based generic views.

Tagged , , , ,

9 comments

  1. mmmm class based generic views.

    Also that pesky not having multi-db thing sunk 2 really big projects for me. Then the PHB thought Python was no good and went PHP! Talk about an over reaction.

    Dace K - 26th October 2009 16:54 - #

  2. Looks like a few of these are Template related -- why not just integrate with Jinja2 and call it done?

    slacy - 26th October 2009 17:02 - #

  3. Looks like you found a post related to Django -- why not just shout Jinja2 Jinja2 Jinja2 all over it?

    (I'm sure I'm not the only person who, exposed to the name of that template library exclusively - and incessantly - by comment trolls, is not remotely disposed to looking at it.)

    John Handelaar - 26th October 2009 17:13 - #

  4. Wow, chill out dude.

    I'm just saying that a lot of the new template features that they're adding / incorporating into Django seem to already be in Jinja. I'm not a comment troll, I'd actually just like to hear some musings from "The Source" (I.e. Simon & Jacob) about why continued parallel development between Django Templates and Jinja2 Templates would be a good thing.

    slacy - 27th October 2009 00:07 - #

  5. @slacy,

    The gist of the argument from the BDFLs (Jacob and Adrian, I don't think Simon took on that role) is that Jinja2 and Django Templates fill different needs.

    From the Django Pony's mouth:

    Designing a template language is a lot like seasoning a dish; there's a whole range of tastes out there. Options range from a language that allows variable substitution and nothing else all the way up to templates that embed a full-featured programming language.

    Like seasoning a dish, we aim Django's template language towards the average. That of course means that a some will find it bland and some will spit it out in disgust.

    My advice to those people is to learn how to cook.

    huxley - 27th October 2009 00:18 - #

  6. @slacy: There is this thing called backwards compatibility. Every single incompatibility between the two systems is a pretty much a 'killer' for the idea of just using Jinja.

    http://jinja.pocoo.org/2/documentation/faq#how-com patible-is-jinja2-with-django

    Luke Plant - 27th October 2009 02:31 - #

  7. What happened to secure cookies? It's not present anywhere.

    I think it would be a good feature to have. It would also be interesting to do things like implement the user messages api using secure cookies rather than storing them in the database.

    Ian Lewis - 27th October 2009 05:29 - #

  8. Ian: it's there, it's just under "Medium Priority" - which means I need to do some more advocacy (and write a bunch more code).

    Simon Willison - 27th October 2009 08:14 - #

  9. The smarter if tag is the one i wanted most!

    brisbane - 28th October 2009 13:08 - #

Sign in with OpenID

Auto-HTML: Line breaks are preserved; URLs will be converted in to links.

Manual XHTML: Enter your own, valid XHTML. Allowed tags are a, p, blockquote, ul, ol, li, dl, dt, dd, em, strong, dfn, code, q, samp, kbd, var, cite, abbr, acronym, sub, sup, br, pre

A django site