as far as why keep private... lets flip it around. Why make it public? what's the benefit of this change?
Having it private means that the API internals can change if necessary
On Tuesday, February 20, 2024 at 10:15:43 AM UTC-5 Gyeong Hoe Koo wrote:
As the documentation says, Django's `_meta` API is core (https://docs.djangoproject.com/en/5.0/ref/models/meta/), but in my knowledge, APIs that start with `_` are private. Table names, etc. are one of the important APIs, and they seem to be pretty stable. Shouldn't we make them public instead of hiding them as private? Any idea why they are kept as `_meta`? I tried to search history on this decision but I cannot get any clues.Thank you.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a4f03954-c0f9-4a55-91f5-e531e3d66518n%40googlegroups.com.
No comments:
Post a Comment