From 8a3a6236d924f8c9ef0421b8215b6fea89a94e90 Mon Sep 17 00:00:00 2001 From: Julia Medina Date: Tue, 10 Jun 2014 10:59:48 -0300 Subject: [PATCH] Settings topic updated --- docs/topics/settings.rst | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/docs/topics/settings.rst b/docs/topics/settings.rst index 44d9128e9..629fac2dd 100644 --- a/docs/topics/settings.rst +++ b/docs/topics/settings.rst @@ -35,22 +35,23 @@ Settings can be populated using different mechanisms, each of which having a different precedence. Here is the list of them in decreasing order of precedence: - 1. Global overrides (most precedence) + 1. Command line options (most precedence) 2. Project settings module 3. Default settings per-command 4. Default global settings (less precedence) -These mechanisms are described in more detail below. +The population of these settings sources is taken care of internally, but a +manual handling is possible using API calls. See the +:ref:`topics-api-settings` topic for reference. -1. Global overrides -------------------- +These mechanisms are described in more detail below. -Global overrides are the ones that take most precedence, and are usually -populated by command-line options. You can also override one (or more) settings -from command line using the ``-s`` (or ``--set``) command line option. +1. Command line options +----------------------- -For more information see the :attr:`~scrapy.settings.Settings.overrides` -Settings attribute. +Arguments provided by the command line are the ones that take most precedence, +overriding any other options. You can explicitly override one (or more) +settings using the ``-s`` (or ``--set``) command line option. .. highlight:: sh -- GitLab