#23982: Clarify how to properly support both Python 2 and 3 for third-party apps
with migrations
--------------------------------------+------------------------------------
Reporter: spookylukey | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.7
Severity: Normal | Resolution:
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 carljm):
Oh, looks like #23455 is already in 1.7.1 (odd that
https://github.com/django/django/commit/e8a08514de6b97de1fce13b6c6b24cf72d1d60d9
doesn't list it as part of the 1.7.1 tag). And I don't think it resulted
in spurious migrations generally, because on Python 3 it will usually have
been a text string already, and on Python 2 unicode and bytes compare
equal so the change doesn't cause a migration. But that also means we can
revert it without causing spurious migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/23982#comment:9>
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.9a693da0e11625367bea59136cf3f4b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
