#23982: Migrations produced under Python 2 require fixing when run under Python
3
-------------------------------+--------------------------------------
Reporter: spookylukey | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by MarkusH):
I ran into a similar issue the other day with one of my 3rd party apps:
https://github.com/MarkusH/django-dynamic-forms/issues/11 regarding
unicode strings. And I think there is another issue somewhere that covers
the byte string serialization in the migration write. I just cannot find
it.
--
Ticket URL: <https://code.djangoproject.com/ticket/23982#comment:3>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.c7cfad8bd9e5d9074652d2b162dea8a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
