#23315: Cannot resolve operation dependencies
-------------------------------------+-------------------------------------
Reporter: gabejackson | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7-rc-2
Severity: Release blocker | Resolution:
Keywords: migrations, | Triage Stage:
autodetector, circular dependency | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by gabejackson):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I further reduced the model to only 2 apps and 4 models. I found out that
the auto-detector is non-deterministic depending on the alphabetical names
of the models.
If you run the project with the class APackage it will fail with "Cannot
resolve operation deps". If you rename APackage to DPackage (DPackage is
alphabetically now later than DeliveryCountry) and run makemigrations
--dry-run again, it works...
Apparently there is some issue with sorting classes alphabetically. Hope
this helps..
--
Ticket URL: <https://code.djangoproject.com/ticket/23315#comment:1>
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.fbd71501615192434fa053bcd550d9b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
