On Saturday, July 6, 2024 at 11:17:35 AM UTC-7 Florian Apolloner wrote:
On Saturday, July 6, 2024 at 12:30:32 AM UTC+2 Mike Edmunds wrote: Incidentally, I thought there was (used to be?) a policy that internal undocumented APIs were fair game for use by third-party libraries, subclassing, etc., so long as they didn't start with an underscore. (But "private" underscore APIs could have breaking changes at any time.) Am I remembering that wrong? Or was internal API stability only guaranteed for patch-level releases? The API stability contract is documented here: https://docs.djangoproject.com/en/5.0/misc/api-stability/ -- Everything documented is considered part of the API, the rest is private.So yeah, it seems like you are remembering that wrong. Heh. The policy was changed in ticket 19728 <https://code.djangoproject.com/ticket/19728>—prior to that, stable "public APIs" included <https://github.com/django/django/commit/132d5822b0651bd0f192388693cb22263e68ddf5#diff-bb0033eaba53a3c2ac4edc8ea69a0144445c8e90ba35948bd243bea7c511294aL16> "everything documented …, *and *all methods that don't begin with an underscore" [emphasis added]. So apparently I haven't looked at Django's api-stability docs in over a decade. (And had a really obscure detail get stuck in my memory. :-) ) - Mike -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f393cbfe-4e67-488c-9b2d-c31580e2b7a9n%40googlegroups.com.
