From c90de33af86aef689f6a11d7ba51e0e7aed27922 Mon Sep 17 00:00:00 2001
From: Pablo Hoffman <pablo@pablohoffman.com>
Date: Mon, 7 Jan 2013 13:16:19 -0200
Subject: [PATCH] add doc about disabling an extension. refs #132

---
 docs/topics/extensions.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/topics/extensions.rst b/docs/topics/extensions.rst
index 71505ae5f..9a4c0bf2c 100644
--- a/docs/topics/extensions.rst
+++ b/docs/topics/extensions.rst
@@ -62,6 +62,17 @@ Not all available extensions will be enabled. Some of them usually depend on a
 particular setting. For example, the HTTP Cache extension is available by default
 but disabled unless the :setting:`HTTPCACHE_ENABLED` setting is set.
 
+Disabling an extension
+======================
+
+In order to disable an extension that comes enabled by default (ie. those
+included in the :setting:`EXTENSIONS_BASE` setting) you must set its order to
+``None``. For example::
+
+    EXTENSIONS = {
+        'scrapy.contrib.corestats.CoreStats': None,
+    }
+
 Writing your own extension
 ==========================