Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Removed confusing comments from the docs.

The settings reference documentation doesn't seem the right place to
invite users to write their own db and cache backends.

Also the actual wording makes the task sound trivial, which is hardly
the case; writing a custom db backend is a very difficult task, and
writing a custom cache backend is full of gotcha.
  • Loading branch information...
commit 2a0ae9b9ecf7a2f835faf7d944f41bf83c316a50 1 parent 19e5cd7
@loic loic authored bmispelon committed
Showing with 1 addition and 5 deletions.
  1. +1 −5 docs/ref/settings.txt
View
6 docs/ref/settings.txt
@@ -183,8 +183,6 @@ The cache backend to use. The built-in cache backends are:
You can use a cache backend that doesn't ship with Django by setting
:setting:`BACKEND <CACHES-BACKEND>` to a fully-qualified path of a cache
backend class (i.e. ``mypackage.backends.whatever.WhateverCache``).
-Writing a whole new cache backend from scratch is left as an exercise
-to the reader; see the other backends for examples.
.. setting:: CACHES-KEY_FUNCTION
@@ -486,9 +484,7 @@ The database backend to use. The built-in database backends are:
You can use a database backend that doesn't ship with Django by setting
``ENGINE`` to a fully-qualified path (i.e.
-``mypackage.backends.whatever``). Writing a whole new database backend from
-scratch is left as an exercise to the reader; see the other backends for
-examples.
+``mypackage.backends.whatever``).
.. setting:: HOST
Please sign in to comment.
Something went wrong with that request. Please try again.