#23844: Use topological sort for migration operation dependency resolution
-------------------------------------+-------------------------------------
Reporter: patrys | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Migrations | 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
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"21e21c7bc2b8bf7ae127e2aa75048a60d05a6e0f"]:
{{{
#!CommitTicketReference repository=""
revision="21e21c7bc2b8bf7ae127e2aa75048a60d05a6e0f"
Fixed #23844 -- Used topological sort for migration operation dependency
resolution.
This removes the concept of equality between operations to guarantee
compatilibity with Python 3.
Python 3 requires equality to result in identical object hashes. It's
impossible to implement a unique hash that preserves equality as
operations such as field creation depend on being able to accept
arbitrary dicts that cannot be hashed reliably.
Thanks Klaas van Schelven for the original patch in
13d613f80011852404198dfafd1f09c0c0ea42e6.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23844#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/064.9d84fd372034b2d743b36982ed3c1e1e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
