#23226: Migrations generated by python2 break when using python3 to migrate
---------------------------------+----------------------------------------
Reporter: morshed.nader@… | Owner: andrewgodwin
Type: Bug | Status: closed
Component: Migrations | Version: 1.7-rc-2
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+----------------------------------------
Comment (by timgraham):
You need to add `from __future__ import unicode_literals` to your
`models.py` before you generate the migration.
--
Ticket URL: <https://code.djangoproject.com/ticket/23226#comment:17>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/081.1f0d7c0043783dac39d10ba3337d7bb1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
