Upcoming changes to Django development version
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_nowandauto_now_addoptions 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
LazyDateshortcut. - Renaming
django.contrib.localflavor.usatodjango.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.
Posted by Adrian Holovaty on April 6, 2007
Comments
Adrian Holovaty April 6, 2007 at 10:22 a.m.
DougN: That's a great topic for the django-developers mailing list. :)
Ben Ye April 13, 2007 at 10:20 a.m.
When is Django launching the 1.0 release?
We started using Django since ver0.91. It's been a good experience. However, since we are building commercial web site, I really hope the system could be build on an official 1.0 release so that we don't have to worry about incompatibility issue in the future.
Markus May 17, 2007 at 7:49 p.m.
I would also really like to know if there is some kind of time window when it will be out..
Also because of the reasons Ben Ye pointed out.
I wondered because I cannot think that the Django Book will use pre-1.0 content.
PS: I have to things I have seen for django.
1. a syntax highlightning file for Django HTML Templates: http://www.vim.org/scripts/script.php...
2. a colorscheme with the "offical" django colors:
http://www.vim.org/scripts/script.php...
Dont know where to put this information.
Comments are closed
To prevent spam, comments are no longer allowed after sixty days.
DougN April 6, 2007 at 9:56 a.m.
I use the auto_now and auto_add_now options extensively, and have had to deal with many of the side effects in save() when dealing with edit_inline. It's a pain, but the benefits have always seemed to out weigh the problems.
Are there plans to provide helpers for getting this functionality back in a cleaner way? Maybe some Decorators for your models save method?
@auto_now('updatted_on')
@auto_add_now('submitted_date')
def save(self):
____super(MyModel).save()