#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 charettes):
Third party applications supporting both Python 2 and 3 should
consistently import `unicode_literals` to avoid such behavior.
Previous changes made sure migrations generated on Python 2 can be run on
Python 3 (and vice versa) but it used `unicode_literals` were used.
The underlying issue here is that `b'foo' == u'foo'` on Python 2 but not
on 3.
--
Ticket URL: <https://code.djangoproject.com/ticket/23982#comment:2>
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.d253a1d78c7d80f664fb210f88360ebc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
