103 ms·

(Author of South here) Nice article - good set of common pitfalls, too. The multiple people one is especially tricky for people when they first encounter it, it

(Author of South here) Nice article - good set of common pitfalls, too. The multiple people one is especially tricky for people when they first encounter it, it seems. I'm hoping I can resolve some of these issues (like the permissions thing) when we start moving parts of the code into Django proper.

ra 14y ago
Just want to thank Andrew for being a good custodian of south.
arocks 14y ago
Thanks for the update and for creating such an indispensable tool. Regarding your last line, is there any plans to integrate South into Django mainline code in the near future? Is there a place to read the philosophy or roadmap for this?
- andrewgodwin 14y ago
  There is, hopefully in a couple of releases' time. There are some posts I made to the mailing list about it a while ago - I can't look them up quickly though - and a talk I did at DjangoCon this year.
crucialfelix 14y ago
I've often gotten bitten by writing migrations in multiple apps during development and then later finding out that a new install can't be run due to circular dependencies. Then its quite tricky to untangle them. Maybe there's a way to do a dry run full migration (fresh install) test or even a check and warning when creating a new migration. of course it usually involves multiple sibling apps that have too much knowledge of each other's FKs. anyway, thanks for south !
hahainternet 14y ago
Do you have a recommended workflow for multiple contributors using Git? Also do you ever intend to fix the django permissions bug that requires a syncdb --all? Not really HN discussion points I guess but I have recently started using South on a project and the lack of clear direction here confused me. This bug has been known for quite a while but I couldn't find any best practise recommendations for either situation.
- andrewgodwin 14y ago
  Unfortunately the permissions thing is really, really tough to fix - and not using Django permissions myself nor in any work projects, one that's rarely high on my priorities, alas. For Git stuff, just make sure you're aware of who is writing migrations where and know what to do when you get a conflict. Making sure you have lots of smaller apps rather than one giant one really helps.

ra 14y ago

Just want to thank Andrew for being a good custodian of south.

arocks 14y ago

Thanks for the update and for creating such an indispensable tool. Regarding your last line, is there any plans to integrate South into Django mainline code in the near future? Is there a place to read the philosophy or roadmap for this?

andrewgodwin 14y ago
There is, hopefully in a couple of releases' time. There are some posts I made to the mailing list about it a while ago - I can't look them up quickly though - and a talk I did at DjangoCon this year.

crucialfelix 14y ago

I've often gotten bitten by writing migrations in multiple apps during development and then later finding out that a new install can't be run due to circular dependencies. Then its quite tricky to untangle them. Maybe there's a way to do a dry run full migration (fresh install) test or even a check and warning when creating a new migration. of course it usually involves multiple sibling apps that have too much knowledge of each other's FKs. anyway, thanks for south !

hahainternet 14y ago

Do you have a recommended workflow for multiple contributors using Git? Also do you ever intend to fix the django permissions bug that requires a syncdb --all? Not really HN discussion points I guess but I have recently started using South on a project and the lack of clear direction here confused me. This bug has been known for quite a while but I couldn't find any best practise recommendations for either situation.

andrewgodwin 14y ago
Unfortunately the permissions thing is really, really tough to fix - and not using Django permissions myself nor in any work projects, one that's rarely high on my priorities, alas. For Git stuff, just make sure you're aware of who is writing migrations where and know what to do when you get a conflict. Making sure you have lots of smaller apps rather than one giant one really helps.