Skip to content

Commit

Permalink
Importing unicode_literals causes a problem in South when importing f…
Browse files Browse the repository at this point in the history
…rom django.db.models.fields because then the name of the model class that is passed into __import__ is unicode, rather than a byte string. I'm not quite sure why this causes a problem importing from this module but not others. However, removing the unicode_literals import from these migrations fixes the issue, and it doesn't look like the migrations have any literals that need to be unicode.
  • Loading branch information
Ben Demboski authored and SeanHayes committed Oct 10, 2015
1 parent b248e7f commit 71eb96f
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion tastypie/south_migrations/0002_add_apikey_index.py
@@ -1,5 +1,4 @@
# -*- coding: utf-8 -*-
from __future__ import unicode_literals
from south.db import db
from south.v2 import SchemaMigration
from tastypie.compat import AUTH_USER_MODEL
Expand Down

0 comments on commit 71eb96f

Please sign in to comment.