Adrian Holovaty and Jacob Kaplan-Moss, BDFLs of Django
The final sessions of DjangoCon was a joint talk between the audience and the two co-founders of Django, Adrian Holovaty and Jacob Kaplan-Moss. The format varied between ticking off lists of itches that the two felt they should scratch and interactive contributions from the audience.
The feel within the the community is that with the launch of 1.0, the sky's the limit for features added to the the versions leading up to 2.0. While the maintainers have committed to maintaining a stable API for the foreseeable future, they're fired up to begin adding new features.
Photo via Brian Veloso
Some of the biggest features that all parties were interested in were in batch editing of objects in the database. Adrian Holovaty named both batch deleting and batch editing of rows directly from the administrative interface as big features he'd like to see in Django.
Jacob mentioned moving the project to a timed release schedule, citing many other open source projects which had done the same with success. Also requested was a method for managing translations of the official Django documentation–none of which exist at the moment.
Also bandied about was some sort of method to tighten up the Django community and tie many of the meta-Django sites like DjangoPlugables, DjangoSnippets, DjangoPeople, and DjangoSearch together (e.g. show all your snippets on your DjangoPeople page and bring your identity and projects from DjangoPeople to DjangoPluggables and so forth).
After the two had exhausted their lists, they opened the floor to the audience to trot out their own ponies. Out of those discussions a large list of requests emerged:
Django should have the best debugging and profiling tools of any web frameworkDiscuss starting to phase out support for Python 2.3Documentation should go further than just your first applicationBetter links from the Django docs to community tutorialsDenormalisation built in to the ORMNamespaces for template tagsA django-stones benchmarkdjango.shortcuts should be better, less boilerplate in views.py pleaseBetter support for writing more complex template tagsRefactor a Django "site" to be just another view functionTimezone support at the model level
And of course, the pinkest pony of them all: Support for multiple database connections (which includes sharding). If the feedback from this conference is any indication, it's very reasonable to assume that Django will be getting an enhanced set of database functionality post-haste.Posted on