#30955: Document the different behavior of migration historical models while
they
have abstract base classes.
--------------------------------------+------------------------------------
Reporter: Shipeng Feng | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 2.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Carlton Gibson):
* stage: Unreviewed => Accepted
Comment:
OK, yes, abstract models are removed from `bases` when generating
historical model state since 6436f1fad9ce51f18735106ac75aeea3d6d1f310.
I'm thinking maybe just "In addition, the concrete base classes …" might
be enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/30955#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.7cd5234c88ef139be48a26b69d29022d%40djangoproject.com.
