Lines Matching refs:configuration
1 :mod:`logging.config` --- Logging configuration
38 Takes the logging configuration from a dictionary. The contents of
42 If an error is encountered during configuration, this function will
57 constructor is passed the dictionary used for configuration, and
66 the returned object to put the configuration into effect::
82 Reads the logging configuration from a :mod:`configparser`\-format file. The
88 configuration).
94 instantiated, and the configuration read by it from the
112 in the logging configuration.
120 * Use of a configuration file where logging configuration is just part
121 of the overall application configuration.
122 * Use of a configuration read from a file, and then modified by the using
151 To send a configuration to the socket, read in the configuration file and
159 Because portions of the configuration are passed through
168 :func:`listen` socket and sending a configuration which runs whatever
182 the configuration, which will use :func:`dictConfig` for configuration.
184 ``False`` in the configuration you send.
197 The logging configuration functionality tries to offer convenience, and in part this
198 is done by offering the ability to convert text in configuration files into Python
199 objects used in logging configuration - for example, as described in
202 configuration) could be used to invoke any code you like, and for this reason you
203 should treat configuration files from untrusted sources with *extreme caution* and
213 Describing a logging configuration requires listing the various
263 format. If your formatter requires different or extra configuration
335 * *root* - this will be the configuration for the root logger.
336 Processing of the configuration will be as for any logger, except
339 * *incremental* - whether the configuration is to be interpreted as
340 incremental to the existing configuration. This value defaults to
341 ``False``, which means that the specified configuration replaces the
342 existing configuration with the same semantics as used by the
345 If the specified value is ``True``, the configuration is processed
359 configuration. For example, because objects such as filters
360 and formatters are anonymous, once a configuration is set up, it is
362 configuration.
366 run-time, once a configuration is set up; the verbosity of loggers and
373 Thus, when the ``incremental`` key of a configuration dict is present
379 Using a value in the configuration dict lets configurations to be sent
397 logger holding a reference to the handler. In the configuration dict,
400 configuration to indicate that a connection exists between the source
409 # configuration for formatter with id 'brief' goes here
411 # configuration for formatter with id 'precise' goes here
414 # configuration of handler with id 'h1' goes here
417 # configuration of handler with id 'h2' goes here
421 # other configuration for logger 'foo.bar.baz'
431 in that they are only meaningful for processing the configuration
433 not persisted anywhere when the configuration call is complete.
449 different instances, so there is no support in this configuration
453 which detail their configuration. In some places, the logging system
459 configuration dictionary and which returns the instantiated object.
484 formatters have configuration sub-dictionaries::
500 configuration sub-dictionary for the third formatter, with id
516 configuration sub-dictionary as keyword arguments. In the above
533 There are times where a configuration needs to refer to objects
534 external to the configuration, for example ``sys.stderr``. If the
535 configuration dict is constructed using Python code, this is
536 straightforward, but a problem arises when the configuration is
539 ``'sys.stderr'``. To facilitate this distinction, the configuration
542 ``'ext://sys.stderr'`` is provided as a value in the configuration,
561 to objects in the configuration. This will be done implicitly by the
562 configuration system for things that it knows about. For example, the
572 the system already knows about this class, then in the configuration,
576 an ``alternate`` handler, the configuration system would not know that
584 # configuration of file handler goes here
592 in the configuration itself rather than the import namespace. The
608 in the configuration, the string ``'cfg://handlers'`` would resolve to
660 The configuration file format understood by :func:`fileConfig` is based on
666 configuration details are held in a section ``[logger_log01]``. Similarly, a
668 configuration held in a section called ``[handler_hand01]``, while a formatter
669 called ``form01`` in the ``[formatters]`` section will have its configuration
671 configuration must be specified in a section called ``[logger_root]``.
680 configuration, you will need to use :func:`dictConfig`. Note that future
681 enhancements to configuration functionality will be added to
714 ``[handlers]`` section and have corresponding sections in the configuration
737 Sections which specify handler configuration are exemplified by the following.
754 a corresponding section in the configuration file.
819 Sections which specify formatter configuration are typified by the following.
830 The arguments for the formatter configuration are the same as the keys