#28746: Model missing custom Meta option in migrations
-------------------------------------+-------------------------------------
Reporter: JP Navarro | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.10
Severity: Normal | Resolution: invalid
Keywords: abstract Meta | Triage Stage:
inheritance | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* component: Database layer (models, ORM) => Migrations
* resolution: => invalid
Comment:
I bisected the behavior change to
50931dfa5310d5ae1c6e2852d05bf1e86700827f. It's seemingly unrelated but I
guess the issue may be related to import changes in that patch and timing
in which the `options.DEFAULT_NAMES` monkeypatch is running. Feel free to
reopen if you do further investigation and find that Django is at fault.
--
Ticket URL: <https://code.djangoproject.com/ticket/28746#comment:6>
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/067.8e5132748f8ba9abe5b5782438ba3fd6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
