On 23 March 2011 14:26, Russell Keith-Magee <russ...@keith-magee.com> wrote: > 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? > > You mean -- other than the release notes [1]?
Hm, banner-blindness maybe, I've never noticed the "The Django open-source project"-section of the main documentation-page before, had to find it by googling :) > 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. I always port to the new stuff as soon as possible due to deprecation-paranoia - when it is deprecated and I *must* upgrade, will the docs and hints and tips about it still be around? Yeah, django is serious about docs, but other projects aren't, and it is effort-saving to treat all projects the same, so... HM -- 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.
