Whither Django? - Russell Keith-Magee (djangocon.eu)

Tags: djangocon, django, zope, python

Whither is archaic English for “where are we going”, “what comes next”? So: what does the future hold for django?

About releases: there’s about 10 months between releases. The good news is that we’re getting closer and closer to the actual planned release date every time. 1.3 was only a few weeks late.

Backwards compatibility is high on django’s list. We’re proud of it. Sometimes things changes, but with a limited amount of effort you can get everything working yet.

Another major thing to be proud of: security. No CSRF problems. No XSS. No database injections. Everything is real safe.

What’s going to be in django 1.4?

For certain (as they’re already committed into trunk):

  • Class-based form wizards.
  • Signed cookies.
  • Configurable admin filters.

Possible (because it depends on work that still needs doing, note also that this list is not fixed as Russell cooked it up himself):

Probably not (as it needs more work and 1.4 features ought to be virtually finished right now):

  • Anything from gsoc 2011:
    • Schema migration.
    • Compiled templates.
    • Composite keys.
    • Template based forms.
  • NoSQL/Query refactor (gsoc 2010).

Well, what’s beyond 1.4? Look at what we’re missing. Well, there’s nothing that’s fundamentally missing. There was a list from a 2004 flickr keynote. Most of those shortcomings have actually been adressed.

Whither or wither?

Whither means “which way are we going”. Wither means “dying on the vine”.

Do we adapt? Where are we going? How do we keep capturing all developers’ imagination? Zope was successful but it is withering now. It isn’t capturing developers’ interest anymore.

Watch out for inertia. We have backwards compatibility, but this means we’re a bit big. And it means that most work is maintenance and corner cases that need proper fixing. Not many high-stepping high-visibility heroic new things. Django is stable now! And that means a lot of work.

So we need volunteers. Django needs more. It is good that they added more core contributors last year.

Again he asks us to work with the core developers, not against them. Ask friendly.

Python 3

The elephant in the room. Now is the time to start being serious about this. (Note by me: read Armin Ronacher’s recent talk at PyGrunn as background material.)

It also means that we have to start looking at django 2. Just some raw brainstorming by Russell:

These aren’t finished discussions! This is something we all have a vested interested in. The community should participate A LOT in this discussion. Django is yours, so participate!

sleeping
blog comments powered by Disqus
 
vanrees.org logo

About me

My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.

Weblog feeds

Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):