Migrate error #1005

Closed
7wonders opened this Issue Aug 10, 2013 · 11 comments

Projects

None yet

6 participants

Getting this error when running migrate

Running migrations for tastypie:

  • Migrating forwards to 0002_add_apikey_index.

    tastypie:0001_initial
    TypeError: type() argument 1 must be string, not unicode

any ideas?

If trying to run it again afterwards, it returns

Running migrations for tastypie:

  • Migrating forwards to 0002_add_apikey_index.

    tastypie:0001_initial
    TypeError: Item in ``from list'' not a string

hmm, seems to work fine with 0.9.15

It was introduced in 23b4a4e

You can fix it by removing from __future__ import unicode_literals from the migration files.

yes, that seems to do the trick

@carlio carlio added a commit to carlio/django-tastypie that referenced this issue Aug 12, 2013
@carlio carlio [refs #1005] Removing use of unicode_literals in migrations, as South…
… requires bytestrings
04602b6
@carlio carlio added a commit to carlio/django-tastypie that referenced this issue Aug 12, 2013
@carlio carlio [refs #1005] Removing unicode_literals from migrations as South expec…
…ts only bytestrings
3dbf87f
carlio commented Aug 12, 2013

Derp - pull request #997 already fixes this, so I closed mine.

@avelino avelino added a commit to opps/opps that referenced this issue Nov 14, 2013
@avelino avelino Set version tastypie 63a9c67
Member

Closing in favor of pull request.

@SeanHayes SeanHayes closed this Oct 10, 2015

Any chance there will be a new release containing this fix since it still only lives in master...?

Member

@benjaoming New release is on PyPi.

Thanks @SeanHayes, much appreciated and congrats on another release!

@benjaoming benjaoming referenced this issue in learningequality/ka-lite Feb 1, 2016
Closed

Use latest tastypie #4797

For the record, if anyone is wondering, this was never merged nor released and thus tastypie 0.12.2, the final version with South support cannot migrate forwards.

Hopefully we've all moved beyond South :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment