I cover some of the new changes in Django 1.2 in this article: http://www.tiemonster.info/a/24005/
Most of this information comes straight from the changelist. Others were things that the core developers must have assumed were common sense, but that I didn't think about when upgrading. If you run across anything that's not on the list, let me know and I'll update the article. -Mark On Jul 29, 3:41 am, knight <alexar...@gmail.com> wrote: > Thank you all for the links and advises. > It really helps me. > > Regards, Alex A. > > On Jul 29, 10:32 am, Russell Keith-Magee <russ...@keith-magee.com> > wrote: > > > On Wed, Jul 28, 2010 at 9:29 PM, Massimiliano Ravelli > > > <massimiliano.rave...@gmail.com> wrote: > > > On Jul 28, 3:13 pm, knight <alexar...@gmail.com> wrote: > > >> What are the minimal changes that I need to make in order to work with > > >> 1.2.1? > > > > Did you have a look > > > athttp://code.djangoproject.com/wiki/BackwardsIncompatibleChanges > > > ? > > > As it says at the top of that wiki page, that page documents the > > backwards incompatible changes that were made in the leadup to Django > > 1.0. > > > If you want migration notes for Django 1.1 or 1.2, you should consult > > the relevant release notes: > > > [1]http://docs.djangoproject.com/en/dev/releases/1.1/ > > [2]http://docs.djangoproject.com/en/dev/releases/1.2/ > > > Yours, > > Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
