From f251dda2687ad0cd21c126580c4ddfff59444d93 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Adri=C3=A1n=20Chaves?= <adrian@chaves.io>
Date: Thu, 21 Nov 2019 11:59:10 +0100
Subject: [PATCH] Make debug doctests pass

---
 docs/topics/debug.rst | 8 ++++++++
 pytest.ini            | 1 -
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/topics/debug.rst b/docs/topics/debug.rst
index 0aaad0c77..4b2588518 100644
--- a/docs/topics/debug.rst
+++ b/docs/topics/debug.rst
@@ -48,6 +48,10 @@ The most basic way of checking the output of your spider is to use the
 of the spider at the method level. It has the advantage of being flexible and
 simple to use, but does not allow debugging code inside a method.
 
+.. highlight:: none
+
+.. skip: start
+
 In order to see the item scraped from a specific url::
 
     $ scrapy parse --spider=myspider -c parse_item -d 2 <item_url>
@@ -85,6 +89,8 @@ using::
 
     $ scrapy parse --spider=myspider -d 3 'http://example.com/page1'
 
+.. skip: end
+
 
 Scrapy Shell
 ============
@@ -94,6 +100,8 @@ spider, it is of little help to check what happens inside a callback, besides
 showing the response received and the output. How to debug the situation when
 ``parse_details`` sometimes receives no item?
 
+.. highlight:: python
+
 Fortunately, the :command:`shell` is your bread and butter in this case (see
 :ref:`topics-shell-inspect-response`)::
 
diff --git a/pytest.ini b/pytest.ini
index 7be5d8572..9d99dcd22 100644
--- a/pytest.ini
+++ b/pytest.ini
@@ -8,7 +8,6 @@ addopts =
     --ignore=docs/_ext
     --ignore=docs/conf.py
     --ignore=docs/news.rst
-    --ignore=docs/topics/debug.rst
     --ignore=docs/topics/developer-tools.rst
     --ignore=docs/topics/dynamic-content.rst
     --ignore=docs/topics/items.rst