#35707: Squash migrations in django.contrib.auth for better performance and
nicer
output
-------------------------------------+-------------------------------------
Reporter: Tim Abbott | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: contrib.auth | Version: 5.0
Severity: Normal | Resolution: wontfix
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 Natalia Bidart):
Hello Tim, thank you for your ticket! I agree with the resolution from
this ticket and with the commentary from Jacob.
Squashing `auth` migrations without a proper deprecation path, and without
considering all the possible scenarios of usage by Django projects, will
likely be a breaking change and the gain does not feel worth producing
that breakage.
Because of the above, this report should be treated similarly to a "new
feature request" for Django. For cases like this, the recommended path
forward is to first propose and discuss the idea/request with the
community and gain consensus. To do that, please consider starting a new
conversation on the [https://forum.djangoproject.com/c/internals/5 Django
Forum], where you'll reach a wider audience and likely get extra feedback.
If the community agrees with the proposal, please return to this ticket
and reference the forum discussion so we can re-open it. For more
information, please refer to
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features the documented guidelines for requesting
features].
--
Ticket URL: <https://code.djangoproject.com/ticket/35707#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701918f15e213-de7ed455-a84c-41d5-b098-7e0ff0db96c8-000000%40eu-central-1.amazonses.com.
