I don't think that's a valid Django migration. You can't simply edit
South migrations to make them Django compatible. Please follow the steps
outlined in the link I provided in my previous message.
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users"
Oops, sorry.
Its my first mezzanine app and django migration.
I'll keep at it.
Thanks.
On Thursday, January 28, 2016 at 7:15:50 PM UTC+3, Eduardo Rivas wrote:
>
> I don't think that's a valid Django migration. You can't simply edit
> South migrations to make them Django compatible. Please
Thanks Eduardo,
I've customised the migration that had south as below:-
# -*- coding: utf-8 -*-
#from south.utils import datetime_utils as datetime
#from south.db import db
#from south.v2 import SchemaMigration
from django.db import models
from django.db import migrations
class
Hi all,
I am using Python 2.7.6, Django 1.8.7, Mezzanine 4.1.0
I've used an app called onepage to help me with the site. As of the last
update, the app uses south on this part:-
from south.utils import datetime_utils as datetime from south.db import db
from south.v2 import SchemaMigration from
Django implemented built-in migrations with the release of 1.7, and South
became obsolete. You will need to create standard migrations for the
application to be compatible with Django 1.7+. The Django docs explain this
with detail.
