#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):
I think when a doc fix is committed here, it should also revert the change
from #23455 (before it gets into a release and causes spurious migrations
to be generated). It's much simpler if we maintain "what you put in is
what you get out" when it comes to text vs bytes in migration
serialization.
--
Ticket URL: <https://code.djangoproject.com/ticket/23982#comment:8>
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.0a3c7470cd458cc1e3237cbfe645b8c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
