#23226: Migrations generated by python2 break when using python3 to migrate
---------------------------------+----------------------------------------
Reporter: morshed.nader@… | Owner: andrewgodwin
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7-rc-2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+----------------------------------------
Changes (by andrewgodwin):
* status: new => assigned
* owner: nobody => andrewgodwin
Comment:
I'm in two minds as to whether we should just force-convert everything to
Unicode in migration files (which obviously is technically changing data,
and might break with strings intended for humans to read), or document
that you should be using unicode for your models files.
There's a potential third outcome here where we fix the state stuff to
convert all model names/field names to unicode, which would solve most
immediate problems. I'll investigate.
--
Ticket URL: <https://code.djangoproject.com/ticket/23226#comment:6>
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.1a5026f1184e25a0f344d5101c1497e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
