Hi all, 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): http://code.djangoproject.com/wiki/NewformsAdminBranch * Removing the LazyDate shortcut. * Renaming django.contrib.localflavor.usa to django.contrib.localflavor.us. The biggest change is probably the newforms-admin functionality. So, the moral of this e-mail is that 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. Here's that page: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges 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: http://groups.google.com/group/django-developers Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
