#12663: Information provided by Model._meta should be documented in
<djangodocs>/models/options/
------------------------------------+---------------------------------------
Reporter: MadeR | Owner: nobody
Status: reopened | Milestone: 1.2
Component: Documentation | Version: 1.2-alpha
Resolution: | Keywords: Model Meta Documentation
Stage: Someday/Maybe | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* status: closed => reopened
* resolution: wontfix =>
* stage: Unreviewed => Someday/Maybe
Comment:
@ubernostrum - Jacob and I spoke briefly about this the other day, in the
context of database routers. Although we didn't come to a final decision,
I think it is inevitable that we will have to formally document at least
parts of _meta. In particular, there are some really ancient parts like
app_label and get_field() that haven't changed, even since pre-magic
removal, aren't really like to change in the future, and if they did
change, would break so much code in the wild that it would be a backwards
incompatibility in practice, if not in name.
I'll mark this someday/maybe since it is on the plan; if someone gets
really enthused, we might be able to make a first cut for 1.2.
--
Ticket URL: <http://code.djangoproject.com/ticket/12663#comment:2>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
