#23982: Clarify how to properly support both Python 2 and 3 for third-party apps
with migrations
-------------------------------------+-------------------------------------
Reporter: spookylukey | Owner: carljm
Type: | Status: closed
Cleanup/optimization | Version: 1.7
Component: Documentation | Resolution: fixed
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carl Meyer <carl@…>):
In [changeset:"b37607193639e25a6c630e8d1b3d3bca0833a652"]:
{{{
#!CommitTicketReference repository=""
revision="b37607193639e25a6c630e8d1b3d3bca0833a652"
[1.7.x] Fixed #23982 -- Added doc note on generating Python 2/3 cross-
compatible migrations.
Thanks Luke Plant for the report, and Tim Graham, Simon Charette, and
Markus
Holtermann for review and discussion.
This is a backport of d4bdddeefe35214f194cb85e40dbb761c206e7fa from
master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23982#comment:13>
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.3e7af080a37aa006b58856dc792bf992%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
