Conversation
2de5402
to
f207a58
Compare
Two things:
http://south.readthedocs.org/en/latest/releasenotes/1.0.2.html Also, can you rebase this off of the current master tip? That just makes it a little easier. |
f207a58
to
032e29e
Compare
I have updated South to 1.0.2 version and rebased this branch on top of the current master tip. |
Need to rebase again since schematic files are removed from master |
032e29e
to
247a6dd
Compare
Rebased on top of master, can be reviewed now. |
Looks like you moved the
However, that should be:
Looks like that's true of all the directories. I think once we fix that, when you do:
it'll stop complaining about missing migrations folders. |
Things done: 1. Update South to version 1.0.2 in requirements.txt using peep 2. Rename all 'migrations' directories to 'south_migrations' 3. Build a new VM and verify that the migrations apply. 4. Run the unit tests and verify nothing is broken. South package present in vendor/packages has not been updated
247a6dd
to
dc10b92
Compare
Oops! It was done correctly before the rebase. I can say that because I did run the tests and all of them passed when I had given the original pull request. But when I did the rebase, I think I did it in a hurry and didn't properly check the result before commit. I have fixed it now. :) |
Things done to upgrade south:
1. Update South to version 1.0.1 in requirements.txt using peep
2. Rename all 'migrations' directories to 'south_migrations'
3. Build a new VM and verify that the migrations apply.
4. Run the unit tests and verify nothing is broken.
South package present in vendor/packages has not been updated