That means that if there’s something you’d like to see in Django 1.1, you need to make your proposal before November 7. Come November 15, we’ll get to see what the Django team will be working on for the next release.
Look for django 1.1 at arrive somewhere around March 16-20.
As outlined in the docs, all minor Django release (1.1, 1.2, etc) should be backwards compatible with earlier 1.x releases, so if you’re writing code for Django 1.0 you should be fine when the next minor version arrives.
For those of you unable to attend, Google has released the videos from the recent Django Conference (see our coverage). Highlights include the DjangoCon keynote from founders Adrian Holovaty and Jacob Kaplan-Moss, as well as the always hilarious Cal Henderson talking about why he hates Django.
Where does Django go from here? That’s the question that closed out the final talk here at DjangoCon, with the co-creators of Django, Adrian Holovaty (above left) and Jacob Kaplan-Moss, addressing their own ideas for the future of the framework and as well as some “I want a pony” suggestions from the audience.
But before they delved into the nuts and bolts of what we can look forward to, both Kaplan-Moss and Holovaty went to great lengths to stress that Django is still not, at least in their minds, a framework, but rather “a way to get shit done.”
Although it could be taken as quip, after two full days of DjangoCon there’s one thing that’s abundantly clear — the core Django developers are extremely informal and very willing to listen too feedback and criticism. In fact Kaplan-Moss repeatedly stressed the importance of the community remaining open to criticism and admitting mistakes as well as fixing them.
So what can you expect in future version of Django? Kaplan-Moss and Holovaty had a number of suggestions for improving the Django admin — multiple delete, multiple edits and more — as well as support for multiple databases, an updated official Django book and more.
Perhaps the most welcome news (judging by audience response) is that Django will, baring serious community objections, move to a timed release schedule.
Other ideas included bringing the Django community sites together; perhaps using OpenID to handle identity, but also perhaps simply bringing together some of the many community sites — Django Snippets, Django People, Django Plugables, etc — so the sites could share data between themselves.
After outlining their own ideas, the pair turned suggestions over to the crowd, which asked for everything from multiple database support (a running theme at the conference) to ORM improvements, as well as dozens of smaller requests.
[Update: Simon Willison has collected up most of the suggestions and entered them in the Django ticket tracker with the keyword DjangoCon; head over to see a complete list of what the people want.]
The only suggestion that was universally booed was rolling Ajax support into Django. As Holovaty suggested, “that’s what JQuery.com is for.”
And that brings the first ever DjangoCon to a close. But be sure to stop by Webmonkey for all the latest Django news as well as some more tutorials.
Andy McCurdy of Whiskey Media, Michael Greer from The Onion and Leah Culver of Pownce talk about the successes their websites have found with Django.
The real test of any web application framework doesn’t involve abstracts like benchmark scores, but rather how well it performs in the wild. Maybe even more important is the big question: is anyone using it to build serious websites?
In the case of Django, the answer is yes. There are already several very large sites running on the framework, proving that, multiple database issues aside, Django can scale. It works for everyone from Google and the Free Software Foundation to The Onion, which is using Django to power its new Decider website.
Sunday afternoon at DjangoCon, attendees got a behind-the-scenes peek at some successful Django sites and the people who run them. In addition to those in the photo above, panelists also included Jason Yan from Disqus, Joshua “jag” Ginsberg from the Free Software Foundation and Matt Croydon of the Lawrence Journal-World.
But the panel guests didn’t limit the discussion to just their sites and what Django does for them. Moderator Jacob Kaplan Moss also asked each developer to offer some background on how and why they came to use Django.
The common theme on the panel? An overwhelming desire to stop using PHP and embrace Python for web development. Given that Django is the current standout option when it comes to using Python on the web, all the panelists eventually found themselves downloading the Django code. And the rest of course is, well, live sites.
We’re deep into the second day of DjangoCon, the two day event dedicated to the open-source web framework. There are some over-arching themes we’re seeing here, mostly involving a lot of self-criticism among Django’s core developers and a lot of discussion about how the framework can be improved and extended so it can better compete with more mature offerings like Rails. Also, you can sense the enthusiasm — everyone’s sporting Django shirts and buttons, chattering away about Django, GeoDjango, Python, and some cool new Django-powered site they heard about at last night’s party.
The hosts here at Google will be posting videos of all the talks soon (we’ll put up a link as soon as one’s available). Attendees are posting photos to Flickr, as are the Webmonkeys. You can also check out the latest tweets using this Twitter widget we whipped up: