On Wed, Mar 23, 2011 at 9:02 PM, Hanne Moa <hanne....@gmail.com> wrote: > Remembering the pain of going from 1.1 to 1.2 (csrf-token), is there > or will there be a guide/one-stop-shop for upgrading from 1.2 to 1.3? > That is: are there other big changes than generic view functions to > generic view classes and could there be an official/canonical page > listing these?
You mean -- other than the release notes [1]? If you cast your mind back, upgrading from 1.1 to 1.2 wasn't a problem -- *unless* you opted into new features like CSRF. The new CSRF handling wasn't turned on by default as the result of an update. The same rules apply this time. If you're not opting into any new features, then upgrading won't require any specific actions, other than addressing any backwards incompatibility issues that affect your specific install (which are all listed in the release notes). As for opting into new features -- well, the depends on the feature you want to adopt. However, the only new feature that should cause require a major effort is modifying your code to use generic views -- and there is a migration guide specifically to describe the issues involved [2] (and that migration guide is linked in the release notes). [1] http://docs.djangoproject.com/en/1.3/releases/1.3/ [2] http://docs.djangoproject.com/en/1.3/topics/generic-views-migration/ Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
