My personal preference is for (4). I don't like the addition of a setting, but it's a setting that most users will be able to ignore (since there is a reasonably sensible default), and it is the most explicit and configurable option available.
My opinion with the current codebase is for (4), but the whole post_syncdb-doing-stuff business has been a problem for South in the past, as well, so I'm somewhat partial to (3) - implementing this would make the discontinuity between migrations and syncdb far less, as core would also have to create the tables first.
Still, that's something I'm happy to look at when I start doing the migration-ish merging early next year - it may not need that many changes at all, as opposed to this, so I'm firmly +1 with (4) as the "it's an extra setting, but literally nobody will use it" option.
Andrew -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
