#25461: Mistake in model _meta API migration guide for multi-table inheritance
-------------------------------+------------------------------------
Reporter: ad-65 | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by timgraham):
I don't think we'll need to add the tests in Django since the old APIs are
removed in master at this point. I guess we can just update the docs and
see if any other reports come in.
About replicating the old APIs in a compatibility library, I understand
the rationale, but I'm not highly enthusiastic about it for the reason
pointed out in the docs:
Although it’s possible to make strictly equivalent replacements of the
old methods, that might not be the best approach. Taking the time to
refactor any field loops to make better use of the new API - and possibly
include fields that were previously excluded - will almost certainly
result in better code
The compatibility library would only be needed for Django 1.7 which is
unsupported.
--
Ticket URL: <https://code.djangoproject.com/ticket/25461#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/063.77c4e49c0b88e6e364dc7ab41aa47f5e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
