From db36a844fc60c00b6ba384cbb0e4861ab54e4c43 Mon Sep 17 00:00:00 2001 From: Mark Henderson Date: Mon, 7 Dec 2015 23:27:47 -0500 Subject: [PATCH] Update options.py Updated verbiage. --- tornado/options.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/tornado/options.py b/tornado/options.py index 861aabee0..40169fb8a 100644 --- a/tornado/options.py +++ b/tornado/options.py @@ -43,10 +43,9 @@ either:: .. note: - When using tornado.options.parse_config_file, the only options that are set - are ones that were previously defined with either tornado.options.parse_command_line - or tornado.options.define. tornado.options.parse_config_file is used mainly as a - means to offer overriding settings for different environments. + When using tornado.options.parse_command_line or + tornado.options.parse_config_file, the only options that are set are + ones that were previously defined with tornado.options.define. Command line formats are what you would expect (``--myoption=myvalue``). Config files are just Python files. Global names become options, e.g.:: -- 2.47.2