39
37
In general, everything covered in the documentation -- with the exception of
40
anything in the :ref:`internals area <internals-index>` is considered stable as
38
anything in the :doc:`internals area </internals/index>` is considered stable as
41
39
of 1.0. This includes these APIs:
43
- :ref:`Authorization <topics-auth>`
41
- :doc:`Authorization </topics/auth>`
45
- :ref:`Caching <topics-cache>`.
47
- :ref:`Model definition, managers, querying and transactions
50
- :ref:`Sending e-mail <topics-email>`.
52
- :ref:`File handling and storage <topics-files>`
54
- :ref:`Forms <topics-forms-index>`
56
- :ref:`HTTP request/response handling <topics-http-index>`, including file
43
- :doc:`Caching </topics/cache>`.
45
- :doc:`Model definition, managers, querying and transactions
48
- :doc:`Sending e-mail </topics/email>`.
50
- :doc:`File handling and storage </topics/files>`
52
- :doc:`Forms </topics/forms/index>`
54
- :doc:`HTTP request/response handling </topics/http/index>`, including file
57
55
uploads, middleware, sessions, URL resolution, view, and shortcut APIs.
59
- :ref:`Generic views <topics-http-generic-views>`.
57
- :doc:`Generic views </topics/http/generic-views>`.
61
- :ref:`Internationalization <topics-i18n>`.
63
- :ref:`Pagination <topics-pagination>`
65
- :ref:`Serialization <topics-serialization>`
67
- :ref:`Signals <topics-signals>`
69
- :ref:`Templates <topics-templates>`, including the language, Python-level
70
:ref:`template APIs <ref-templates-index>`, and :ref:`custom template tags
71
and libraries <howto-custom-template-tags>`. We may add new template
59
- :doc:`Internationalization </topics/i18n/index>`.
61
- :doc:`Pagination </topics/pagination>`
63
- :doc:`Serialization </topics/serialization>`
65
- :doc:`Signals </topics/signals>`
67
- :doc:`Templates </topics/templates>`, including the language, Python-level
68
:doc:`template APIs </ref/templates/index>`, and :doc:`custom template tags
69
and libraries </howto/custom-template-tags>`. We may add new template
72
70
tags in the future and the names may inadvertently clash with
73
71
external template tags. Before adding any such tags, we'll ensure that
74
72
Django raises an error if it tries to load tags with duplicate names.
76
- :ref:`Testing <topics-testing>`
74
- :doc:`Testing </topics/testing>`
78
- :ref:`django-admin utility <ref-django-admin>`.
80
- :ref:`Built-in middleware <ref-middleware>`
82
- :ref:`Request/response objects <ref-request-response>`.
84
- :ref:`Settings <ref-settings>`. Note, though that while the :ref:`list of
85
built-in settings <ref-settings>` can be considered complete we may -- and
76
- :doc:`django-admin utility </ref/django-admin>`.
78
- :doc:`Built-in middleware </ref/middleware>`
80
- :doc:`Request/response objects </ref/request-response>`.
82
- :doc:`Settings </ref/settings>`. Note, though that while the :doc:`list of
83
built-in settings </ref/settings>` can be considered complete we may -- and
86
84
probably will -- add new settings in future versions. This is one of those
87
85
places where "'stable' does not mean 'complete.'"
89
- :ref:`Built-in signals <ref-signals>`. Like settings, we'll probably add
87
- :doc:`Built-in signals </ref/signals>`. Like settings, we'll probably add
90
88
new signals in the future, but the existing ones won't break.
92
- :ref:`Unicode handling <ref-unicode>`.
90
- :doc:`Unicode handling </ref/unicode>`.
94
- Everything covered by the :ref:`HOWTO guides <howto-index>`.
92
- Everything covered by the :doc:`HOWTO guides </howto/index>`.
99
97
Most of the modules in ``django.utils`` are designed for internal use. Only
100
the following parts of :ref:`django.utils <ref-utils>` can be considered stable:
98
the following parts of :doc:`django.utils </ref/utils>` can be considered stable:
102
100
- ``django.utils.cache``
103
101
- ``django.utils.datastructures.SortedDict`` -- only this single class; the