#34856: Running tests with historical migrations that contain index together
fails
with TypeError.
-------------------------------+--------------------------------------
Reporter: Sage Abdullah | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: dev
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 Sage Abdullah):
Replying to [comment:3 David Sanders]:
> PS: If you disagree with the removal at the end of deprecation feel free
to start a thread on the Django forum:
https://www.djangoproject.com/community/
Thanks! I don't mind the removal itself, though I wonder if the release
notes should be updated to better reflect the fact that squashing the
migrations will be mandatory? The current wording seems to suggest it's
optional. That said, this ticket is probably enough as additional
documentation about this issue if anyone else encounters it in the future.
--
Ticket URL: <https://code.djangoproject.com/ticket/34856#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/0107018ab31be4cd-41fd1c3a-1f6e-4334-87fe-d0666e577015-000000%40eu-central-1.amazonses.com.
