#35711: Running migrate with disabled migrations fails with version 5.1
----------------------------+--------------------------------------
Reporter: Mounir | Owner: (none)
Type: Bug | Status: closed
Component: Migrations | Version: 5.1
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by Simon Charette):
I created a new project using 5.1, assigned `None` to each entry in
`MIGRATION_MODULES`, and ran `migrate --run-syncdb` without any issues.
You might have to provide a project that reproduces I'm afraid as I
audited the entire autodetector modue for `add_operation` calls passing
`dependencies` (which are the ones adding `_auto_deps`) and also used type
checking and found no violations. At this point I suspect you might use a
third-party app that overrides the `migrate` management command.
--
Ticket URL: <https://code.djangoproject.com/ticket/35711#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070191991eba6a-0553cac2-4524-4c74-8efa-b46904ee3c19-000000%40eu-central-1.amazonses.com.
