-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting ready for Django 1.7 #1559
Comments
This won't be done because of backward compatibility. |
So... can we use DRF with 1.7 or is this 1 migration a blocker? |
@rapilabs you can use DRF with Django 1.7 unless you use authtoken. |
It is possible to support both south migrations and the new 1.7 migrations, see http://treyhunner.com/2014/03/migrating-to-django-1-dot-7/ |
@dekkers I am aware of this. If someone can come up with a pull request for this I'll consider merging it after I'm sure it doesn't break things. |
@xordoquy For a project that doesn't require backwards compatability, but does require authtoken, is it possible to somehow workaround this issue, other than forking and patching the migration myself? |
Closed in favor of #1653 |
…into encode#1559 Conflicts: docs/topics/release-notes.md
There's only 1 migration in the DRF codebase but it will need to either be removed or updated for Django 1.7.
Looks like South 2 is a way off being finished so until then it's not clear how best to handle migrations in a way that will work for Django 1.7 and earlier versions.
The text was updated successfully, but these errors were encountered: