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
Update to Django 1.7 #37
Conversation
👍 |
ec11058
to
6cb4ed0
Compare
ea7bfa1
to
ba6d2de
Compare
Updated to handle converting from South to Django migrations. Ready to be looked at again. Should be tested upgrading packages from 0.3, 0.4 and 0.5. |
echo 'Faking the 0.4 migration' | ||
/usr/share/python/archivematica-storage-service/bin/python manage.py migrate locations 0002_v0_4 --fake | ||
fi | ||
if [[ $2 == '0.6.'* || $2 == '0.5.'* ]]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check with Justin that these actually match the versions postinst will be called with.
Haven't tested but looks good 👍 |
ba6d2de
to
009b0b1
Compare
009b0b1
to
1adb672
Compare
Added south migration for 0.7 |
👍 |
1adb672
to
190a114
Compare
refs #7305 mimetype is deprecated in Django 1.7, replaced by content_type
refs #7307 Update Django and Tastypie versions. Update test runner default to suppress warnings. Remove South, as it is built in now.
Remove patterns, and rely on stock Python regex behaviour.
refs #7307 To support upgrading from 0.3 and later, add Django migrations for each of those releases. Fake apply those migrations in postinst for more recent releases. All migrations for after 0.7 should be created solely as Django migrations
190a114
to
ad019be
Compare
Update to use Django 1.7, including fixes for backwards compatibliity and other versions bumps.