[mezzanine-users] South Migration Issue

2016-01-28 Thread George M
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.db import models 

Any attempts to deploy are met with errors below

There is no South database module 'south.db.postgresql_psycopg2' for your 
database. Please either choose a supported database, check for 
SOUTH_DATABASE_ADAPTER[S] settings, or remove South from INSTALLED_APPS.
  or
django.db.migrations.loader.BadMigrationError: Migrated app u'onepage' 
contains South migrations. Make sure all numbered South migrations are 
deleted prior to creating Django migrations.

I have tried installing and uninstalling south to no avail. It seems I have 
to use south regardless.
Is there a known work around to this?
Any help is appreciated..

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [mezzanine-users] South Migration Issue

2016-01-28 Thread Eduardo Rivas
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.

https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [mezzanine-users] South Migration Issue

2016-01-28 Thread George M
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 Migration(migrations.Migration):

def forwards(apps, schema_editor):
# Adding field 'Page.in_opd'
migrations.AddField(
model_name=u'pages_page',
name=u'in_opd',
field='django.db.models.fields.BooleanField',
preserve_default=False
)

def backwards(apps, schema_editor):
# Deleting field 'Page.in_opd'
migrations.RemoveField(
model_name=u'pages_page',
name=u'in_opd'
)
models = {
u'pages.link': {
'Meta': {'ordering': "(u'_order',)", 'object_name': 'Link', 
'_ormbases': [u'pages.Page']},
u'page_ptr': ('django.db.models.fields.related.OneToOneField', 
[], {'to': u"apps.get_model('pages.Page')", 'unique': 'True', 
'primary_key': 'True'})
},
...

Is there anything am not doing right coz its not showing up for migration 
with python manage.py migrate onepage..

On Thursday, January 28, 2016 at 6:08:35 PM UTC+3, Eduardo Rivas wrote:
>
> 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. 
>
>
> https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [mezzanine-users] South Migration Issue

2016-01-28 Thread Eduardo Rivas
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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [mezzanine-users] South Migration Issue

2016-01-28 Thread George M
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 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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.