Common Practices

This section documents common practices when using Scrapy. These are things that cover many topics and don’t often fall into any other specific section.

Run Scrapy from a script

You can use the API to run Scrapy from a script, instead of the typical way of running Scrapy via scrapy crawl.

Remember that Scrapy is built on top of the Twisted asynchronous networking library, so you need to run it inside the Twisted reactor.

The first utility you can use to run your spiders is scrapy.crawler.CrawlerProcess. This class will start a Twisted reactor for you, configuring the logging and setting shutdown handlers. This class is the one used by all Scrapy commands.

Here’s an example showing how to run a single spider with it.

  1. import scrapy
  2. from scrapy.crawler import CrawlerProcess
  3. class MySpider(scrapy.Spider):
  4. # Your spider definition
  5. ...
  6. process = CrawlerProcess(settings={
  7. "FEEDS": {
  8. "items.json": {"format": "json"},
  9. },
  10. })
  11. process.crawl(MySpider)
  12. process.start() # the script will block here until the crawling is finished

Define settings within dictionary in CrawlerProcess. Make sure to check CrawlerProcess documentation to get acquainted with its usage details.

If you are inside a Scrapy project there are some additional helpers you can use to import those components within the project. You can automatically import your spiders passing their name to CrawlerProcess, and use get_project_settings to get a Settings instance with your project settings.

What follows is a working example of how to do that, using the testspiders project as example.

  1. from scrapy.crawler import CrawlerProcess
  2. from scrapy.utils.project import get_project_settings
  3. process = CrawlerProcess(get_project_settings())
  4. # 'followall' is the name of one of the spiders of the project.
  5. process.crawl('followall', domain='')
  6. process.start() # the script will block here until the crawling is finished

There’s another Scrapy utility that provides more control over the crawling process: scrapy.crawler.CrawlerRunner. This class is a thin wrapper that encapsulates some simple helpers to run multiple crawlers, but it won’t start or interfere with existing reactors in any way.

Using this class the reactor should be explicitly run after scheduling your spiders. It’s recommended you use CrawlerRunner instead of CrawlerProcess if your application is already using Twisted and you want to run Scrapy in the same reactor.

Note that you will also have to shutdown the Twisted reactor yourself after the spider is finished. This can be achieved by adding callbacks to the deferred returned by the CrawlerRunner.crawl method.

Here’s an example of its usage, along with a callback to manually stop the reactor after MySpider has finished running.

  1. from twisted.internet import reactor
  2. import scrapy
  3. from scrapy.crawler import CrawlerRunner
  4. from scrapy.utils.log import configure_logging
  5. class MySpider(scrapy.Spider):
  6. # Your spider definition
  7. ...
  8. configure_logging({'LOG_FORMAT': '%(levelname)s: %(message)s'})
  9. runner = CrawlerRunner()
  10. d = runner.crawl(MySpider)
  11. d.addBoth(lambda _: reactor.stop())
  12. # the script will block here until the crawling is finished

See also

Reactor Overview

Running multiple spiders in the same process

By default, Scrapy runs a single spider per process when you run scrapy crawl. However, Scrapy supports running multiple spiders per process using the internal API.

Here is an example that runs multiple spiders simultaneously:

  1. import scrapy
  2. from scrapy.crawler import CrawlerProcess
  3. from scrapy.utils.project import get_project_settings
  4. class MySpider1(scrapy.Spider):
  5. # Your first spider definition
  6. ...
  7. class MySpider2(scrapy.Spider):
  8. # Your second spider definition
  9. ...
  10. settings = get_project_settings()
  11. process = CrawlerProcess(settings)
  12. process.crawl(MySpider1)
  13. process.crawl(MySpider2)
  14. process.start() # the script will block here until all crawling jobs are finished

Same example using CrawlerRunner:

  1. import scrapy
  2. from twisted.internet import reactor
  3. from scrapy.crawler import CrawlerRunner
  4. from scrapy.utils.log import configure_logging
  5. from scrapy.utils.project import get_project_settings
  6. class MySpider1(scrapy.Spider):
  7. # Your first spider definition
  8. ...
  9. class MySpider2(scrapy.Spider):
  10. # Your second spider definition
  11. ...
  12. configure_logging()
  13. settings = get_project_settings()
  14. runner = CrawlerRunner(settings)
  15. runner.crawl(MySpider1)
  16. runner.crawl(MySpider2)
  17. d = runner.join()
  18. d.addBoth(lambda _: reactor.stop())
  19. # the script will block here until all crawling jobs are finished

Same example but running the spiders sequentially by chaining the deferreds:

  1. from twisted.internet import reactor, defer
  2. from scrapy.crawler import CrawlerRunner
  3. from scrapy.utils.log import configure_logging
  4. from scrapy.utils.project import get_project_settings
  5. class MySpider1(scrapy.Spider):
  6. # Your first spider definition
  7. ...
  8. class MySpider2(scrapy.Spider):
  9. # Your second spider definition
  10. ...
  11. configure_logging()
  12. settings = get_project_settings()
  13. runner = CrawlerRunner(settings)
  14. @defer.inlineCallbacks
  15. def crawl():
  16. yield runner.crawl(MySpider1)
  17. yield runner.crawl(MySpider2)
  18. reactor.stop()
  19. crawl()
  20. # the script will block here until the last crawl call is finished

Different spiders can set different values for the same setting, but when they run in the same process it may be impossible, by design or because of some limitations, to use these different values. What happens in practice is different for different settings:

See also

Run Scrapy from a script.

Distributed crawls

Scrapy doesn’t provide any built-in facility for running crawls in a distribute (multi-server) manner. However, there are some ways to distribute crawls, which vary depending on how you plan to distribute them.

If you have many spiders, the obvious way to distribute the load is to setup many Scrapyd instances and distribute spider runs among those.

If you instead want to run a single (big) spider through many machines, what you usually do is partition the urls to crawl and send them to each separate spider. Here is a concrete example:

First, you prepare the list of urls to crawl and put them into separate files/urls:


Then you fire a spider run on 3 different Scrapyd servers. The spider would receive a (spider) argument part with the number of the partition to crawl:

  1. curl -d project=myproject -d spider=spider1 -d part=1
  2. curl -d project=myproject -d spider=spider1 -d part=2
  3. curl -d project=myproject -d spider=spider1 -d part=3

Avoiding getting banned

Some websites implement certain measures to prevent bots from crawling them, with varying degrees of sophistication. Getting around those measures can be difficult and tricky, and may sometimes require special infrastructure. Please consider contacting commercial support if in doubt.

Here are some tips to keep in mind when dealing with these kinds of sites:

  • rotate your user agent from a pool of well-known ones from browsers (google around to get a list of them)

  • disable cookies (see COOKIES_ENABLED) as some sites may use cookies to spot bot behaviour

  • use download delays (2 or higher). See DOWNLOAD_DELAY setting.

  • if possible, use Google cache to fetch pages, instead of hitting the sites directly

  • use a pool of rotating IPs. For example, the free Tor project or paid services like ProxyMesh. An open source alternative is scrapoxy, a super proxy that you can attach your own proxies to.

  • use a highly distributed downloader that circumvents bans internally, so you can just focus on parsing clean pages. One example of such downloaders is Zyte Smart Proxy Manager

If you are still unable to prevent your bot getting banned, consider contacting commercial support.