Hi Andrew, hi Trey, as part of the migration to Django 1.7 I just mentioned in my post about the AppConfig, I've obviously also looked into migrations and I am a big fan :) For reference, the project in question is django-fancypages [1].
The route the I have taken for now is the same one described in Trey's blog post. Specifically variant 3) which uses 'migrations' for Django migrations and 'south_migrations' for South. For now, I've documented the setting 'SOUTH_MIGRATION_MODULES' as a requirement for pre-1.7 projects. This seems a good enough solution for now and I'm happy to encourage people to move to Django 1.7 by making it a bit easier. The one thing that I am currently struggling with a bit is how to ensure consistency of both migrations whenever a model changes happens. Do you have any suggestions on how to deal with that? Is there a more sensible way than putting a couple of scripts together that, e.g. run migrations in different Django version and then run tests for migrations checking the schema of both. Any suggestions on that? I might be overthinking this but I don't like it when I have to remember these things...I'm bad at that. Thanks for you input on this and thanks to Andrew and anyone who helped getting this amazing migrations framework into Django 1.7! -- Cheers, Seb [1] https://github.com/tangentlabs/django-fancypages
signature.asc
Description: OpenPGP digital signature
