Deprecations not listed within release notes

[Murat Sert]

There are some deprecations such as the custom_sql_for_model and couple of other methods within django.core.management.sql file which isn't listed on any of the release notes 1.8/1.9/1.11 or deprecation timeline.

Does anyone know if there methods are deprecated or moved elsewhere?

[Antonis Christofides]

Hello,

was custom_sql_for_model ever documented in the Django documentation? If not, then it is (or was) an internal API. Internal APIs can change without notice, and if you use them you do so at your own risk.

Regards,

Antonis

Antonis Christofides
http://djangodeployment.com

On 2018-01-15 14:16, Murat Sert wrote:

There are some deprecations such as the custom_sql_for_model and couple of other methods within django.core.management.sql file which isn't listed on any of the release notes 1.8/1.9/1.11 or deprecation timeline.

Does anyone know if there methods are deprecated or moved elsewhere?

--
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...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/aba23083-90dc-4204-9316-aacc5ae50b4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tim Graham]

Correct, that falls under "private API removal". If you clone the Django source code you can use "git log -S custom_sql_for_model" to find the commits that touched something with that name. In this case, you'll find https://github.com/django/django/commit/4aa089a9a9504c4a833eee8161be013206da5d15.