#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 andrewgodwin):
So, I have opted to fix this by making everything in the model options
state a text type when creating it from live models; this fixes the
problem for me for every model option I can think of (I've got a big file
with them all set to various things)
If someone can replicate the issue _in a crashing manner_ then please re-
open; I'm fine with leaving things like choices= set to bytes types, as
this is actually what the models file says and doing any conversion there
could lead to issues.
--
Ticket URL: <https://code.djangoproject.com/ticket/23226#comment:12>
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.48695b41a0bb21d6ba1786a2e021065d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
