I’m getting this error when I use ‘startmigration’ in South.
My guess is that I have data that is not serializable.
What is the best way for me to determine the offending model?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I solved this by removing the problematic field, applying the migration, adding the field again and doing another migration.
My problem was an inconsistency with a field name that I renamed and some previous migrations that were trying to find it. What would also probably work (and perhaps a better solution) is to edit the migration scripts in
<app>/migrationsto match the new field name.I had to do this when updating the project in the production environment.