Weblog

April archive

Django at Web 2.0 Expo

April 10, 2007

Next week's Web 2.0 Expo in San Francisco features two Django-related presentations.

First, there's the session All You Need To Know About Django:

You've heard about Django, the relatively young Python web framework. But why are people talking about it? Hear lead developer/co-creator Adrian Holovaty explain how the framework works, how it saves you time, and why people fall in love with it. Expect both a high-level overview and low-level code samples, along with a look into Django's future.

Then, it'll be a panel, Comparing Web Application Frameworks:

Creators and architects of a select group of today's most modern, successful web development frameworks will come together in this panel to answer questions from developers.

See you in San Francisco. No word yet whether we'll put together a Django "Birds of a Feather" session, but if you'll be around, leave a comment here so we can coordinate.

Week in review: April 8

April 8, 2007

Django's version 0.96 just landed, but we're already hard at work on the next version. Here's a rundown of some of the bigger improvements we've made to the Django development version in the past week:

  • As of changeset 4901, we've added the ability to name URL patterns. This is a great help with reverse URL matching. See the new docs.
  • Have you seen django.contrib.localflavor yet? An example of our "batteries included" philosophy, it's a collection of functions and data structures that are useful for locale-specific applications. The biggest part of localflavor at this point are django.newforms-style Field objects that validate an assortment of country-specific data. For example, we've got validators for U.S. Social Security numbers, phone numbers, states and ZIP codes; post codes in Australia, Brazil, Finland, France, Germany, Italy, Japan, Norway, and the U.K; and government identity numbers for a number of countries. Plus, we've got more coming. If you can think of (and, better yet, implement) some locale-specific logic that would be useful to a number of people and localflavor doesn't yet handle, please contribute!
  • Work progresses on the newforms-admin branch, which aims to integrate Django's admin site with the newforms library. Along the way, we're taking the opportunity to add extra customization hooks to the admin site. Much of the implementation is done already, and it's now possible, using the branch, to run multiple instances of the Django admin site, with different configuration, in the same Django project. This is exciting stuff; see the status section of the wiki page for some examples of what's changed.
  • We created a unicode branch this week. Malcolm Tredinnick will be taking the lead on making all of Django's internals fully Unicode-aware, once and for all. See the branch wiki page for more info.

Upcoming changes to Django development version

April 6, 2007

For a long time, we've recommended that people use the Django development version instead of the latest Django release, as we try hard to keep the development version stable. We're loosening that policy, temporarily, for the immediate future, in order to make a number of backwards-incompatible changes to the development version.

Examples of some of these changes are:

  • Removing the auto_now and auto_now_add options in Django models.
  • Finishing and merging the "newforms-admin" branch, which changes the way admin options are specified (and gives you a lot more flexibility).
  • Removing the LazyDate shortcut.
  • Renaming django.contrib.localflavor.usa to django.contrib.localflavor.us.

The biggest change is probably the newforms-admin functionality.

Therefore, if you use the Django development version in production settings (as many people, including I, do), take a look at the "Backwards-incompatible changes" wiki page before updating your Django code to make sure your code won't break.

If you use a specific Django release, such as 0.96, you have nothing to worry about. You simply may have to make some changes to your code when you upgrade to the next Django release.

This is, we hope, the final run of backwards-incompatible changes before version 1.0, at which point we'll be committed to compatibility.

If you'd like to discuss these changes, feel free to post a message to the django-developers mailing list.

Interview with Jacob

April 5, 2007

Jacob was recently interviewed by pythonthreads.com. Check it out.