#35772: Document models.Field.contribute_to_class
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
Type: | Gama
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: contribute_to_class | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Clifford Gama):
Hello! and thank you, Natalia, for the detailed review and the community
resources on `contribute_to_class` -- they were very informative.
I'm not very much in favour of making `contribute_to_class` a part of the
public API, so I will not start a discussion in the forum for that.
However, if we agree that, as it currently stands, `contribute_to_class`
is "an undocumented, private, internal API" then I believe we should also
remove it from the docs entirely, since having it there canonises it as
part of the public API, in which case it would have to be officially
documented. Having it in there while maintaining its status as a private
part of the API is a bit in the gray area.
--
Ticket URL: <https://code.djangoproject.com/ticket/35772#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701920a497448-722a0ba3-a9a9-424c-86e2-5bfa67f70b23-000000%40eu-central-1.amazonses.com.
