Django migrations - #95
Merged
Merged
Conversation
Create Django migrations, deprecate South.
Member
|
@Kelketek Looks good, 👍 once you get a green build. |
Kelketek
force-pushed
the
django-migrations
branch
from
January 25, 2016 14:32
d29a584 to
910114c
Compare
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move old migrations into south_migrations folder, create new folder with Django 1.8 migrations.
Use the same basic procedure as in #94 but this time install the requirements.txt for problem-builder, since the master version requires a newer version of xblockutils.
In addition, check to see if you can get the answer sharing block to work between a couple of users, as that will verify the table is there and working.
@itsjeyd