Scrapy, a fast high-level web crawling & scraping framework for Python.
Remove the unexisting retry_complete signal from the documentation
Adrián Chaves4ef38d925e0d
diff --git a/docs/topics/downloader-middleware.rst b/docs/topics/downloader-middleware.rstindex 8dbe249fa..9988ab18b 100644--- a/docs/topics/downloader-middleware.rst+++ b/docs/topics/downloader-middleware.rst@@ -834,8 +834,6 @@ RetryMiddlewareFailed pages are collected on the scraping process and rescheduled at theend, once the spider has finished crawling all regular (non failed) pages.-Once there are no more failed pages to retry, this middleware sends a signal-(retry_complete), so other extensions could connect to that signal.The :class:`RetryMiddleware` can be configured through the followingsettings (see the settings documentation for more info):diff --git a/scrapy/downloadermiddlewares/retry.py b/scrapy/downloadermiddlewares/retry.pyindex 07e979628..dbc605a4c 100644--- a/scrapy/downloadermiddlewares/retry.py+++ b/scrapy/downloadermiddlewares/retry.py@@ -7,9 +7,7 @@ RETRY_TIMES - how many times to retry a failed pageRETRY_HTTP_CODES - which HTTP response codes to retryFailed pages are collected on the scraping process and rescheduled at the end,-once the spider has finished crawling all regular (non failed) pages. Once-there is no more failed pages to retry this middleware sends a signal-(retry_complete), so other extensions could connect to that signal.+once the spider has finished crawling all regular (non failed) pages."""import logging