#30029: Generate migration dependencies in a deterministic order
-------------------------------------+-------------------------------------
Reporter: Dakota Hawkins | Owner: Dakota
Type: | Hawkins
Cleanup/optimization | Status: closed
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution: wontfix
Keywords: migrations, | Triage Stage: Accepted
makemigrations |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: assigned => closed
* resolution: => wontfix
Comment:
After a bit more thought I agree with your conclusion Dakota, setting a
fixed `PYTHONHASHSEED` is probably the sanest way of dealing with that
given a lot more than just `Migration.dependecies` is likely to be ordered
differently for a different seed.
Closing as ''wontfix'' because this can be worked around in the rare cases
when ordering matters for your workflow. Feel free to file another ticket
to allow the exclusion of the header through the `makemigrations` command.
--
Ticket URL: <https://code.djangoproject.com/ticket/30029#comment:6>
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/071.231d2c57e1a0e689a31cec55002f59c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
