On Fri, Apr 1, 2011 at 12:01 AM, Luke Plant <l.plant...@cantab.net> wrote: > On 31/03/11 19:35, Patryk Zawadzki wrote: >> * for 1.4 provide a number of fallback settings that can be used to >> enable legacy behavior in each of the first three points > but this is where it falls down, because the devil is in the details > with regards to backwards compatibility. > > Settings to control this is not really an option, because it means you > have to get everything upgraded together, which is just infeasible with > the current app ecosystem. For each bullet point, you'll need a more > fine-grained approach that allows upgrading at least on the level of an > individual app, and users of that app to be able to use old apps.
I meant a set of separate settings. Like a list of apps that should still use legacy table names. As for template loading, the ticket I mentioned in the original post has a backwards-compatible patch. A future version of Django can just remove the fallback part of the code. The hardest part is making the internals work with fully qualified paths. > We would also need tools to migrate existing tables. Don't forget the > contenttypes app, which contains data that use the existing app names. > Remember also that we don't have any tools in core for upgrading > existing tables or data. It would be much easier if Django contained a migration mechanism that apps such as the content types framework could use. We also have to support a way to convert existing fixtures. > This sounds to me more like the kind of change we might do for Django > 2.0, not 1.4... I hope that it would be possible to roll these out gradually. newforms didn't happen overnight either :) -- Patryk Zawadzki I solve problems. -- 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.
