chunk_id stringlengths 36 36 | source stringclasses 35
values | source_url stringlengths 0 290 | upstream_license stringclasses 1
value | document_id stringlengths 36 36 | chunk_index int64 0 324k | retrieved_at stringclasses 2
values | chunker_version stringclasses 4
values | content_hash stringlengths 15 64 | content stringlengths 50 44.7k | namespace stringclasses 9
values | source_name stringclasses 35
values | raw_text stringlengths 50 44.7k | cleaned_text stringlengths 50 44.7k | tags stringclasses 49
values | collection_name stringclasses 11
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
f3703e59-2503-4a43-b410-2a916b10a01c | CPython Docs | file://datasets/cpython/Doc/library/email.utils.rst | unknown | 04cae1ce-9a25-42b8-81e8-3c087b322e62 | 29,901 | supabase-export-v2 | 057b32f42e35b549 | to override this default, but may be useful certain cases, such as a constructing distributed system that uses a consistent domain name across multiple hosts.
.. versionchanged:: 3.2
Added the *domain* keyword. | trusted_official_docs | CPython Docs | to override this default, but may be useful certain cases, such as a constructing distributed system that uses a consistent domain name across multiple hosts.
.. versionchanged:: 3.2
Added the *domain* keyword. | to override this default, but may be useful certain cases, such as a constructing distributed system that uses a consistent domain name across multiple hosts.
.. versionchanged:: 3.2
Added the *domain* keyword. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
fecc7b54-50f6-451c-b6e5-85757dba064c | CPython Docs | file://datasets/cpython/Doc/library/email.utils.rst | unknown | 04cae1ce-9a25-42b8-81e8-3c087b322e62 | 29,907 | supabase-export-v2 | b94d9c6233760ad1 | If *str* ends and begins with double quotes, they are stripped off. Likewise if *str* ends and begins with angle brackets, they are stripped off.
.. function:: parseaddr(address, *, strict=True) | trusted_official_docs | CPython Docs | If *str* ends and begins with double quotes, they are stripped off. Likewise if *str* ends and begins with angle brackets, they are stripped off.
.. function:: parseaddr(address, *, strict=True) | If *str* ends and begins with double quotes, they are stripped off. Likewise if *str* ends and begins with angle brackets, they are stripped off.
.. function:: parseaddr(address, *, strict=True) | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
0b391b54-7541-4fb1-9638-267442e5345d | CPython Docs | file://datasets/cpython/Doc/library/i18n.rst | unknown | 679b5796-b507-436e-802a-36790f0a2768 | 29,953 | supabase-export-v2 | 4a7e75f44ebb31cb | of language and locale by providing mechanisms for selecting a language to be used in program messages or by tailoring output to match local conventions.
The list of modules described in this chapter is: | trusted_official_docs | CPython Docs | of language and locale by providing mechanisms for selecting a language to be used in program messages or by tailoring output to match local conventions.
The list of modules described in this chapter is: | of language and locale by providing mechanisms for selecting a language to be used in program messages or by tailoring output to match local conventions.
The list of modules described in this chapter is: | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
3f9e2bd3-d0c0-4167-82f1-e60693c72c1f | CPython Docs | file://datasets/cpython/Doc/library/i18n.rst | unknown | 679b5796-b507-436e-802a-36790f0a2768 | 29,952 | supabase-export-v2 | 37f5c6114a53e54d | ******************** Internationalization ********************
The modules described in this chapter help you write software that is
independent of language and locale by providing mechanisms for selecting a
language to be used in program messages or by tailoring output to match local
conventions. | trusted_official_docs | CPython Docs | ******************** Internationalization ********************
The modules described in this chapter help you write software that is
independent of language and locale by providing mechanisms for selecting a
language to be used in program messages or by tailoring output to match local
conventions. | ******************** Internationalization ********************
The modules described in this chapter help you write software that is
independent of language and locale by providing mechanisms for selecting a
language to be used in program messages or by tailoring output to match local
conventions. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
01b6440a-aa1a-41b2-9c00-e3ea311b6d92 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,065 | supabase-export-v2 | 870eafb8c97d8942 | my.package.customFormatterFactory(bar='baz', spam=99.9, answer=42)
.. warning:: The values for keys such as ``bar``, ``spam`` and ``answer`` in
the above example should not be configuration dictionaries or references such
as ``cfg://foo`` or ``ext://bar``, because they will not be processed by the
configuration mach... | trusted_official_docs | CPython Docs | my.package.customFormatterFactory(bar='baz', spam=99.9, answer=42)
.. warning:: The values for keys such as ``bar``, ``spam`` and ``answer`` in
the above example should not be configuration dictionaries or references such
as ``cfg://foo`` or ``ext://bar``, because they will not be processed by the
configuration mach... | my.package.customFormatterFactory(bar='baz', spam=99.9, answer=42)
.. warning:: The values for keys such as ``bar``, ``spam`` and ``answer`` in
the above example should not be configuration dictionaries or references such
as ``cfg://foo`` or ``ext://bar``, because they will not be processed by the
configuration mach... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
0282f963-0781-4754-bfac-dc40ce0a952c | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,023 | supabase-export-v2 | 8980f9ee2df8d604 | .. code-block:: yaml
handlers:
console:
class : logging.StreamHandler
formatter: brief
level : INFO
filters: [allow_foo]
stream : ext://sys.stdout
file:
class : logging.handlers.RotatingFileHandler
formatter: precise
filename: logconfig.log
maxBytes: 1024
backupCount: 3 | trusted_official_docs | CPython Docs | .. code-block:: yaml
handlers:
console:
class : logging.StreamHandler
formatter: brief
level : INFO
filters: [allow_foo]
stream : ext://sys.stdout
file:
class : logging.handlers.RotatingFileHandler
formatter: precise
filename: logconfig.log
maxBytes: 1024
backupCount: 3 | .. code-block:: yaml
handlers:
console:
class : logging.StreamHandler
formatter: brief
level : INFO
filters: [allow_foo]
stream : ext://sys.stdout
file:
class : logging.handlers.RotatingFileHandler
formatter: precise
filename: logconfig.log
maxBytes: 1024
backupCount: 3 | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
0b95ef5b-f1d9-481d-9028-bec3f42dbfb8 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,971 | supabase-export-v2 | 59b36ab14905ddd9 | has a callable attribute :attr:`dictConfigClass` which is initially set to :class:`DictConfigurator`. You can replace the value of :attr:`dictConfigClass` with a suitable implementation of your own.
:func:`dictConfig` calls :attr:`dictConfigClass` passing
the specified dictionary, and then calls the :meth:`configure` ... | trusted_official_docs | CPython Docs | has a callable attribute :attr:`dictConfigClass` which is initially set to :class:`DictConfigurator`. You can replace the value of :attr:`dictConfigClass` with a suitable implementation of your own.
:func:`dictConfig` calls :attr:`dictConfigClass` passing
the specified dictionary, and then calls the :meth:`configure` ... | has a callable attribute :attr:`dictConfigClass` which is initially set to :class:`DictConfigurator`. You can replace the value of :attr:`dictConfigClass` with a suitable implementation of your own.
:func:`dictConfig` calls :attr:`dictConfigClass` passing
the specified dictionary, and then calls the :meth:`configure` ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
131d8fd4-dfa3-48c8-84e4-7b69fb4f2aea | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,066 | supabase-export-v2 | 5a7c5b249036ee66 | configuration dictionaries or references such as ``cfg://foo`` or ``ext://bar``, because they will not be processed by the configuration machinery, but passed to the callable as-is.
The key ``'()'`` has been used as the special key because it is not a
valid keyword parameter name, and so will not clash with the names o... | trusted_official_docs | CPython Docs | configuration dictionaries or references such as ``cfg://foo`` or ``ext://bar``, because they will not be processed by the configuration machinery, but passed to the callable as-is.
The key ``'()'`` has been used as the special key because it is not a
valid keyword parameter name, and so will not clash with the names o... | configuration dictionaries or references such as ``cfg://foo`` or ``ext://bar``, because they will not be processed by the configuration machinery, but passed to the callable as-is.
The key ``'()'`` has been used as the special key because it is not a
valid keyword parameter name, and so will not clash with the names o... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
13789a27-4ead-46e9-bbfd-eacabbc7f167 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,006 | supabase-export-v2 | 7be41779bc7000e0 | the schema version. The only valid value at present is 1, but having this key allows the schema to evolve while still preserving backwards compatibility.
All other keys are optional, but if present they will be interpreted
as described below. In all cases below where a 'configuring dict' is
mentioned, it will be checke... | trusted_official_docs | CPython Docs | the schema version. The only valid value at present is 1, but having this key allows the schema to evolve while still preserving backwards compatibility.
All other keys are optional, but if present they will be interpreted
as described below. In all cases below where a 'configuring dict' is
mentioned, it will be checke... | the schema version. The only valid value at present is 1, but having this key allows the schema to evolve while still preserving backwards compatibility.
All other keys are optional, but if present they will be interpreted
as described below. In all cases below where a 'configuring dict' is
mentioned, it will be checke... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
159b4067-034f-46fe-84fe-83a9992c6823 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,041 | supabase-export-v2 | 5629b62bc3884055 | in a safe way is problematic in a multi-threaded environment; while not impossible, the benefits are not worth the complexity it adds to the implementation.
Thus, when the ``incremental`` key of a configuration dict is present
and is ``True``, the system will completely ignore any ``formatters`` and
``filters`` entries... | trusted_official_docs | CPython Docs | in a safe way is problematic in a multi-threaded environment; while not impossible, the benefits are not worth the complexity it adds to the implementation.
Thus, when the ``incremental`` key of a configuration dict is present
and is ``True``, the system will completely ignore any ``formatters`` and
``filters`` entries... | in a safe way is problematic in a multi-threaded environment; while not impossible, the benefits are not worth the complexity it adds to the implementation.
Thus, when the ``incremental`` key of a configuration dict is present
and is ``True``, the system will completely ignore any ``formatters`` and
``filters`` entries... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
1a5610e4-4184-4d3a-b32e-6425e7bb459f | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,009 | supabase-export-v2 | 3a5c90d502041b95 | be a dict in which each key is a formatter id and each value is a dict describing how to configure the corresponding :class:`~logging.Formatter` instance.
The configuring dict is searched for the following optional keys
which correspond to the arguments passed to create a
:class:`~logging.Formatter` object: | trusted_official_docs | CPython Docs | be a dict in which each key is a formatter id and each value is a dict describing how to configure the corresponding :class:`~logging.Formatter` instance.
The configuring dict is searched for the following optional keys
which correspond to the arguments passed to create a
:class:`~logging.Formatter` object: | be a dict in which each key is a formatter id and each value is a dict describing how to configure the corresponding :class:`~logging.Formatter` instance.
The configuring dict is searched for the following optional keys
which correspond to the arguments passed to create a
:class:`~logging.Formatter` object: | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
2611ddd8-6254-4630-afee-8def04d8552d | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,071 | supabase-export-v2 | 3ec9052914f41fa0 | the returned formatter will have attribute ``foo`` set to ``'bar'`` and attribute ``baz`` set to ``'bozz'``.
.. warning:: The values for attributes such as ``foo`` and ``baz`` in
the above example should not be configuration dictionaries or references such
as ``cfg://foo`` or ``ext://bar``, because they will not be p... | trusted_official_docs | CPython Docs | the returned formatter will have attribute ``foo`` set to ``'bar'`` and attribute ``baz`` set to ``'bozz'``.
.. warning:: The values for attributes such as ``foo`` and ``baz`` in
the above example should not be configuration dictionaries or references such
as ``cfg://foo`` or ``ext://bar``, because they will not be p... | the returned formatter will have attribute ``foo`` set to ``'bar'`` and attribute ``baz`` set to ``'bozz'``.
.. warning:: The values for attributes such as ``foo`` and ``baz`` in
the above example should not be configuration dictionaries or references such
as ``cfg://foo`` or ``ext://bar``, because they will not be p... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
26ed1000-cfdb-4f2e-abed-681ace6cd86e | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,012 | supabase-export-v2 | 44a28e9863a32275 | alternative class might present exception tracebacks in an expanded or condensed format. If your formatter requires different or extra configuration keys, you should use :ref:`logging-config-dict-userdef`.
* *filters* - the corresponding value will be a dict in which each key
is a filter id and each value is a dict de... | trusted_official_docs | CPython Docs | alternative class might present exception tracebacks in an expanded or condensed format. If your formatter requires different or extra configuration keys, you should use :ref:`logging-config-dict-userdef`.
* *filters* - the corresponding value will be a dict in which each key
is a filter id and each value is a dict de... | alternative class might present exception tracebacks in an expanded or condensed format. If your formatter requires different or extra configuration keys, you should use :ref:`logging-config-dict-userdef`.
* *filters* - the corresponding value will be a dict in which each key
is a filter id and each value is a dict de... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
26ef4436-321d-4d54-bedb-9de2c4b2c9a7 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,969 | supabase-export-v2 | dd8b59b4428822c8 | a :exc:`ValueError`, :exc:`TypeError`, :exc:`AttributeError` or :exc:`ImportError` with a suitably descriptive message. The following is a (possibly incomplete) list of conditions which will raise an error:
* A ``level`` which is not a string or which is a string not
corresponding to an actual logging level. * A ``pro... | trusted_official_docs | CPython Docs | a :exc:`ValueError`, :exc:`TypeError`, :exc:`AttributeError` or :exc:`ImportError` with a suitably descriptive message. The following is a (possibly incomplete) list of conditions which will raise an error:
* A ``level`` which is not a string or which is a string not
corresponding to an actual logging level. * A ``pro... | a :exc:`ValueError`, :exc:`TypeError`, :exc:`AttributeError` or :exc:`ImportError` with a suitably descriptive message. The following is a (possibly incomplete) list of conditions which will raise an error:
* A ``level`` which is not a string or which is a string not
corresponding to an actual logging level. * A ``pro... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
2815e788-a91c-47c0-9493-f9bfb0d3d674 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,157 | supabase-export-v2 | 8f034068afed516e | The arguments for the formatter configuration are the same as the keys in the dictionary schema :ref:`formatters section <logging-config-dictschema-formatters>`.
The ``defaults`` entry, when :ref:`evaluated <func-eval>` in the context of
the ``logging`` package's namespace, is a dictionary of default values for
custom ... | trusted_official_docs | CPython Docs | The arguments for the formatter configuration are the same as the keys in the dictionary schema :ref:`formatters section <logging-config-dictschema-formatters>`.
The ``defaults`` entry, when :ref:`evaluated <func-eval>` in the context of
the ``logging`` package's namespace, is a dictionary of default values for
custom ... | The arguments for the formatter configuration are the same as the keys in the dictionary schema :ref:`formatters section <logging-config-dictschema-formatters>`.
The ``defaults`` entry, when :ref:`evaluated <func-eval>` in the context of
the ``logging`` package's namespace, is a dictionary of default values for
custom ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
2b6d0c4e-ac95-413c-9262-861a8969e40f | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,108 | supabase-export-v2 | 8756627dd99371d9 | returns the queue instance to use. That callable could be a :class:`queue.Queue` subclass or a function which returns a suitable queue instance, such as ``my.module.queue_factory()``.
* A dict with a ``'()'`` key which is constructed in the usual way as discussed in
:ref:`logging-config-dict-userdef`. The result of th... | trusted_official_docs | CPython Docs | returns the queue instance to use. That callable could be a :class:`queue.Queue` subclass or a function which returns a suitable queue instance, such as ``my.module.queue_factory()``.
* A dict with a ``'()'`` key which is constructed in the usual way as discussed in
:ref:`logging-config-dict-userdef`. The result of th... | returns the queue instance to use. That callable could be a :class:`queue.Queue` subclass or a function which returns a suitable queue instance, such as ``my.module.queue_factory()``.
* A dict with a ``'()'`` key which is constructed in the usual way as discussed in
:ref:`logging-config-dict-userdef`. The result of th... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
2cd49e51-ebb7-471e-b396-68e7f23a7c1b | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,968 | supabase-export-v2 | 5d3600766989ce43 | Takes the logging configuration from a dictionary. The contents of this dictionary are described in :ref:`logging-config-dictschema` below.
If an error is encountered during configuration, this function will
raise a :exc:`ValueError`, :exc:`TypeError`, :exc:`AttributeError`
or :exc:`ImportError` with a suitably descr... | trusted_official_docs | CPython Docs | Takes the logging configuration from a dictionary. The contents of this dictionary are described in :ref:`logging-config-dictschema` below.
If an error is encountered during configuration, this function will
raise a :exc:`ValueError`, :exc:`TypeError`, :exc:`AttributeError`
or :exc:`ImportError` with a suitably descr... | Takes the logging configuration from a dictionary. The contents of this dictionary are described in :ref:`logging-config-dictschema` below.
If an error is encountered during configuration, this function will
raise a :exc:`ValueError`, :exc:`TypeError`, :exc:`AttributeError`
or :exc:`ImportError` with a suitably descr... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
2cd8e8a3-78da-43df-b391-1b66df6770ac | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,024 | supabase-export-v2 | e63a9e3c50299a9c | class : logging.StreamHandler formatter: brief level : INFO filters: [allow_foo] stream : ext://sys.stdout file: class : logging.handlers.RotatingFileHandler formatter: precise filename: logconfig.log maxBytes: 1024 backupCount: 3
the handler with id ``console`` is instantiated as a
:class:`logging.StreamHandler`, usi... | trusted_official_docs | CPython Docs | class : logging.StreamHandler formatter: brief level : INFO filters: [allow_foo] stream : ext://sys.stdout file: class : logging.handlers.RotatingFileHandler formatter: precise filename: logconfig.log maxBytes: 1024 backupCount: 3
the handler with id ``console`` is instantiated as a
:class:`logging.StreamHandler`, usi... | class : logging.StreamHandler formatter: brief level : INFO filters: [allow_foo] stream : ext://sys.stdout file: class : logging.handlers.RotatingFileHandler formatter: precise filename: logconfig.log maxBytes: 1024 backupCount: 3
the handler with id ``console`` is instantiated as a
:class:`logging.StreamHandler`, usi... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
35562593-c9e2-4fef-855a-94401ca68815 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,050 | supabase-export-v2 | 5c68904a1b00cde2 | (Note: YAML used here because it's a little more readable than the equivalent Python source form for the dictionary.)
The ids for loggers are the logger names which would be used
programmatically to obtain a reference to those loggers, e.g. ``foo.bar.baz``. The ids for Formatters and Filters can be any string
value (su... | trusted_official_docs | CPython Docs | (Note: YAML used here because it's a little more readable than the equivalent Python source form for the dictionary.)
The ids for loggers are the logger names which would be used
programmatically to obtain a reference to those loggers, e.g. ``foo.bar.baz``. The ids for Formatters and Filters can be any string
value (su... | (Note: YAML used here because it's a little more readable than the equivalent Python source form for the dictionary.)
The ids for loggers are the logger names which would be used
programmatically to obtain a reference to those loggers, e.g. ``foo.bar.baz``. The ids for Formatters and Filters can be any string
value (su... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
362e9f12-9df6-4d6c-ae7c-752849cfd833 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,083 | supabase-export-v2 | 3dcb83e488076555 | be converted to the value ``logging.DEBUG``, and the ``handlers``, ``filters`` and ``formatter`` entries will take an object id and resolve to the appropriate destination object.
However, a more generic mechanism is needed for user-defined
objects which are not known to the :mod:`logging` module. For
example, consider ... | trusted_official_docs | CPython Docs | be converted to the value ``logging.DEBUG``, and the ``handlers``, ``filters`` and ``formatter`` entries will take an object id and resolve to the appropriate destination object.
However, a more generic mechanism is needed for user-defined
objects which are not known to the :mod:`logging` module. For
example, consider ... | be converted to the value ``logging.DEBUG``, and the ``handlers``, ``filters`` and ``formatter`` entries will take an object id and resolve to the appropriate destination object.
However, a more generic mechanism is needed for user-defined
objects which are not known to the :mod:`logging` module. For
example, consider ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
37aeea36-ca44-4707-959e-be6b524abb9b | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,100 | supabase-export-v2 | 1551a15a5ae225cb | Configuring QueueHandler and QueueListener """"""""""""""""""""""""""""""""""""""""""
If you want to configure a :class:`~logging.handlers.QueueHandler`, noting that this
is normally used in conjunction with a :class:`~logging.handlers.QueueListener`, you
can configure both together. After the configuration, the ``Queu... | trusted_official_docs | CPython Docs | Configuring QueueHandler and QueueListener """"""""""""""""""""""""""""""""""""""""""
If you want to configure a :class:`~logging.handlers.QueueHandler`, noting that this
is normally used in conjunction with a :class:`~logging.handlers.QueueListener`, you
can configure both together. After the configuration, the ``Queu... | Configuring QueueHandler and QueueListener """"""""""""""""""""""""""""""""""""""""""
If you want to configure a :class:`~logging.handlers.QueueHandler`, noting that this
is normally used in conjunction with a :class:`~logging.handlers.QueueListener`, you
can configure both together. After the configuration, the ``Queu... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
3d1484ab-c8e2-48c1-be0a-2d6a47ffb36f | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,105 | supabase-export-v2 | c531eb811cdb2d20 | If the ``queue`` key is present, the corresponding value can be one of the following:
* An object implementing the :meth:`Queue.put_nowait <queue.Queue.put_nowait>`
and :meth:`Queue.get <queue.Queue.get>` public API. For instance, this may be
an actual instance of :class:`queue.Queue` or a subclass thereof, or a prox... | trusted_official_docs | CPython Docs | If the ``queue`` key is present, the corresponding value can be one of the following:
* An object implementing the :meth:`Queue.put_nowait <queue.Queue.put_nowait>`
and :meth:`Queue.get <queue.Queue.get>` public API. For instance, this may be
an actual instance of :class:`queue.Queue` or a subclass thereof, or a prox... | If the ``queue`` key is present, the corresponding value can be one of the following:
* An object implementing the :meth:`Queue.put_nowait <queue.Queue.put_nowait>`
and :meth:`Queue.get <queue.Queue.get>` public API. For instance, this may be
an actual instance of :class:`queue.Queue` or a subclass thereof, or a prox... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
42cdde48-d45d-4a2b-a53f-29bc09ed4877 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,988 | supabase-export-v2 | 7463386b26833439 | :class:`~threading.Thread` instance on which you can call :meth:`~threading.Thread.start` to start the server, and which you can :meth:`~threading.Thread.join` when appropriate. To stop the server, call :func:`stopListening`.
The ``verify`` argument, if specified, should be a callable which should
verify whether bytes... | trusted_official_docs | CPython Docs | :class:`~threading.Thread` instance on which you can call :meth:`~threading.Thread.start` to start the server, and which you can :meth:`~threading.Thread.join` when appropriate. To stop the server, call :func:`stopListening`.
The ``verify`` argument, if specified, should be a callable which should
verify whether bytes... | :class:`~threading.Thread` instance on which you can call :meth:`~threading.Thread.start` to start the server, and which you can :meth:`~threading.Thread.join` when appropriate. To stop the server, call :func:`stopListening`.
The ``verify`` argument, if specified, should be a callable which should
verify whether bytes... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
42d69547-d3a7-4087-af74-e866194aef0a | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,141 | supabase-export-v2 | f02155a1a180ef5d | class (as determined by :func:`eval` in the ``logging`` package's namespace). The ``level`` is interpreted as for loggers, and ``NOTSET`` is taken to mean 'log everything'.
The ``formatter`` entry indicates the key name of the formatter for this
handler. If blank, a default formatter (``logging._defaultFormatter``) is ... | trusted_official_docs | CPython Docs | class (as determined by :func:`eval` in the ``logging`` package's namespace). The ``level`` is interpreted as for loggers, and ``NOTSET`` is taken to mean 'log everything'.
The ``formatter`` entry indicates the key name of the formatter for this
handler. If blank, a default formatter (``logging._defaultFormatter``) is ... | class (as determined by :func:`eval` in the ``logging`` package's namespace). The ``level`` is interpreted as for loggers, and ``NOTSET`` is taken to mean 'log everything'.
The ``formatter`` entry indicates the key name of the formatter for this
handler. If blank, a default formatter (``logging._defaultFormatter``) is ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
44631ff3-44a3-4cc7-b158-2ea63747759e | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,132 | supabase-export-v2 | c3b5ed6f95c68459 | the root logger only, ``NOTSET`` means that all messages will be logged. Level values are :ref:`evaluated <func-eval>` in the context of the ``logging`` package's namespace.
The ``handlers`` entry is a comma-separated list of handler names, which must
appear in the ``[handlers]`` section. These names must appear in the... | trusted_official_docs | CPython Docs | the root logger only, ``NOTSET`` means that all messages will be logged. Level values are :ref:`evaluated <func-eval>` in the context of the ``logging`` package's namespace.
The ``handlers`` entry is a comma-separated list of handler names, which must
appear in the ``[handlers]`` section. These names must appear in the... | the root logger only, ``NOTSET`` means that all messages will be logged. Level values are :ref:`evaluated <func-eval>` in the context of the ``logging`` package's namespace.
The ``handlers`` entry is a comma-separated list of handler names, which must
appear in the ``[handlers]`` section. These names must appear in the... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
44ed21c6-8841-4567-bdc4-8c144e0e0f7b | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,113 | supabase-export-v2 | bbc908ef6715191f | * A string which resolves to a class which is a subclass of ``QueueListener``, such as ``'my.package.CustomListener'``.
* A dict with a ``'()'`` key which is constructed in the usual way as discussed in
:ref:`logging-config-dict-userdef`. The result of this construction should be a
callable with the same signature as... | trusted_official_docs | CPython Docs | * A string which resolves to a class which is a subclass of ``QueueListener``, such as ``'my.package.CustomListener'``.
* A dict with a ``'()'`` key which is constructed in the usual way as discussed in
:ref:`logging-config-dict-userdef`. The result of this construction should be a
callable with the same signature as... | * A string which resolves to a class which is a subclass of ``QueueListener``, such as ``'my.package.CustomListener'``.
* A dict with a ``'()'`` key which is constructed in the usual way as discussed in
:ref:`logging-config-dict-userdef`. The result of this construction should be a
callable with the same signature as... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
4529d4aa-7021-45a0-88fa-1ac7e99b9a9a | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,070 | supabase-export-v2 | 2f88a0d94e81a8fb | { '()' : 'my.package.customFormatterFactory', 'bar' : 'baz', 'spam' : 99.9, 'answer' : 42, '.' { 'foo': 'bar', 'baz': 'bozz' } }
the returned formatter will have attribute ``foo`` set to ``'bar'`` and
attribute ``baz`` set to ``'bozz'``. | trusted_official_docs | CPython Docs | { '()' : 'my.package.customFormatterFactory', 'bar' : 'baz', 'spam' : 99.9, 'answer' : 42, '.' { 'foo': 'bar', 'baz': 'bozz' } }
the returned formatter will have attribute ``foo`` set to ``'bar'`` and
attribute ``baz`` set to ``'bozz'``. | { '()' : 'my.package.customFormatterFactory', 'bar' : 'baz', 'spam' : 99.9, 'answer' : 42, '.' { 'foo': 'bar', 'baz': 'bozz' } }
the returned formatter will have attribute ``foo`` set to ``'bar'`` and
attribute ``baz`` set to ``'bozz'``. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
4aa72d64-1e61-493a-88b5-59481d929569 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,973 | supabase-export-v2 | 07826b3a4f9236a8 | def dictConfig(config): dictConfigClass(config).configure()
For example, a subclass of :class:`DictConfigurator` could call
``DictConfigurator.__init__()`` in its own :meth:`__init__`, then
set up custom prefixes which would be usable in the subsequent
:meth:`configure` call. :attr:`dictConfigClass` would be bound t... | trusted_official_docs | CPython Docs | def dictConfig(config): dictConfigClass(config).configure()
For example, a subclass of :class:`DictConfigurator` could call
``DictConfigurator.__init__()`` in its own :meth:`__init__`, then
set up custom prefixes which would be usable in the subsequent
:meth:`configure` call. :attr:`dictConfigClass` would be bound t... | def dictConfig(config): dictConfigClass(config).configure()
For example, a subclass of :class:`DictConfigurator` could call
``DictConfigurator.__init__()`` in its own :meth:`__init__`, then
set up custom prefixes which would be usable in the subsequent
:meth:`configure` call. :attr:`dictConfigClass` would be bound t... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
4f3f52ab-9fd9-42ac-9076-50fce2d5c3c8 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,992 | supabase-export-v2 | 5473eb4d9f76afaa | by connecting to the victim's :func:`listen` socket and sending a configuration which runs whatever code the attacker wants to have executed in the victim's process.
This is
especially easy to do if the default port is used, but not hard even if a
different port is used. To avoid the risk of this happening, use the
... | trusted_official_docs | CPython Docs | by connecting to the victim's :func:`listen` socket and sending a configuration which runs whatever code the attacker wants to have executed in the victim's process.
This is
especially easy to do if the default port is used, but not hard even if a
different port is used. To avoid the risk of this happening, use the
... | by connecting to the victim's :func:`listen` socket and sending a configuration which runs whatever code the attacker wants to have executed in the victim's process.
This is
especially easy to do if the default port is used, but not hard even if a
different port is used. To avoid the risk of this happening, use the
... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
4f8145f6-4211-4f69-abc3-8f23e8d5282a | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,013 | supabase-export-v2 | c28fc5efa5a4e849 | be a dict in which each key is a filter id and each value is a dict describing how to configure the corresponding Filter instance.
The configuring dict is searched for the key ``name`` (defaulting to the
empty string) and this is used to construct a :class:`logging.Filter`
instance. | trusted_official_docs | CPython Docs | be a dict in which each key is a filter id and each value is a dict describing how to configure the corresponding Filter instance.
The configuring dict is searched for the key ``name`` (defaulting to the
empty string) and this is used to construct a :class:`logging.Filter`
instance. | be a dict in which each key is a filter id and each value is a dict describing how to configure the corresponding Filter instance.
The configuring dict is searched for the key ``name`` (defaulting to the
empty string) and this is used to construct a :class:`logging.Filter`
instance. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
4fa425de-5143-40d6-85d1-251df63c4d16 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,079 | supabase-export-v2 | 761c181a236956db | provided as a value in the configuration, then the ``ext://`` will be stripped off and the remainder of the value processed using normal import mechanisms.
The handling of such prefixes is done in a way analogous to protocol
handling: there is a generic mechanism to look for prefixes which
match the regular expression ... | trusted_official_docs | CPython Docs | provided as a value in the configuration, then the ``ext://`` will be stripped off and the remainder of the value processed using normal import mechanisms.
The handling of such prefixes is done in a way analogous to protocol
handling: there is a generic mechanism to look for prefixes which
match the regular expression ... | provided as a value in the configuration, then the ``ext://`` will be stripped off and the remainder of the value processed using normal import mechanisms.
The handling of such prefixes is done in a way analogous to protocol
handling: there is a generic mechanism to look for prefixes which
match the regular expression ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
4fd6c03d-e011-4ee8-b959-7c6cb29838d8 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,115 | supabase-export-v2 | 07d18cc56f3f336d | If the ``listener`` key is absent, :class:`logging.handlers.QueueListener` is used.
The values under the ``handlers`` key are the names of other handlers in the
configuration (not shown in the above snippet) which will be passed to the queue
listener. | trusted_official_docs | CPython Docs | If the ``listener`` key is absent, :class:`logging.handlers.QueueListener` is used.
The values under the ``handlers`` key are the names of other handlers in the
configuration (not shown in the above snippet) which will be passed to the queue
listener. | If the ``listener`` key is absent, :class:`logging.handlers.QueueListener` is used.
The values under the ``handlers`` key are the names of other handlers in the
configuration (not shown in the above snippet) which will be passed to the queue
listener. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
500b5fcc-b269-481b-9d80-8df61db7f0bc | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,058 | supabase-export-v2 | 82d45ee884d37c4c | formatters: brief: format: '%(message)s' default: format: '%(asctime)s %(levelname)-8s %(name)-15s %(message)s' datefmt: '%Y-%m-%d %H:%M:%S' custom: (): my.package.customFormatterFactory bar: baz spam: 99.9 answer: 42
The above YAML snippet defines three formatters. The first, with id
``brief``, is a standard :class:`l... | trusted_official_docs | CPython Docs | formatters: brief: format: '%(message)s' default: format: '%(asctime)s %(levelname)-8s %(name)-15s %(message)s' datefmt: '%Y-%m-%d %H:%M:%S' custom: (): my.package.customFormatterFactory bar: baz spam: 99.9 answer: 42
The above YAML snippet defines three formatters. The first, with id
``brief``, is a standard :class:`l... | formatters: brief: format: '%(message)s' default: format: '%(asctime)s %(levelname)-8s %(name)-15s %(message)s' datefmt: '%Y-%m-%d %H:%M:%S' custom: (): my.package.customFormatterFactory bar: baz spam: 99.9 answer: 42
The above YAML snippet defines three formatters. The first, with id
``brief``, is a standard :class:`l... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
54c7e86b-907f-41ac-acc3-21e399378222 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,069 | supabase-export-v2 | bf2cbd6e0e4e0896 | attribute names to values. If found, the specified attributes will be set on the user-defined object before it is returned. Thus, with the following configuration::
{
'()' : 'my.package.customFormatterFactory',
'bar' : 'baz',
'spam' : 99.9,
'answer' : 42,
'.' {
'foo': 'bar',
'baz': 'bozz'
}
} | trusted_official_docs | CPython Docs | attribute names to values. If found, the specified attributes will be set on the user-defined object before it is returned. Thus, with the following configuration::
{
'()' : 'my.package.customFormatterFactory',
'bar' : 'baz',
'spam' : 99.9,
'answer' : 42,
'.' {
'foo': 'bar',
'baz': 'bozz'
}
} | attribute names to values. If found, the specified attributes will be set on the user-defined object before it is returned. Thus, with the following configuration::
{
'()' : 'my.package.customFormatterFactory',
'bar' : 'baz',
'spam' : 99.9,
'answer' : 42,
'.' {
'foo': 'bar',
'baz': 'bozz'
}
} | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
56484297-8d35-457d-ba64-95a4ed0528ef | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,114 | supabase-export-v2 | b17b1f5889b541b0 | in the usual way as discussed in :ref:`logging-config-dict-userdef`. The result of this construction should be a callable with the same signature as the ``QueueListener`` initializer.
If the ``listener`` key is absent, :class:`logging.handlers.QueueListener` is used. | trusted_official_docs | CPython Docs | in the usual way as discussed in :ref:`logging-config-dict-userdef`. The result of this construction should be a callable with the same signature as the ``QueueListener`` initializer.
If the ``listener`` key is absent, :class:`logging.handlers.QueueListener` is used. | in the usual way as discussed in :ref:`logging-config-dict-userdef`. The result of this construction should be a callable with the same signature as the ``QueueListener`` initializer.
If the ``listener`` key is absent, :class:`logging.handlers.QueueListener` is used. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
59294434-250c-4788-a034-cade5cd58e13 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,090 | supabase-export-v2 | 6962b318612eebe7 | handlers: email: class: logging.handlers.SMTPHandler mailhost: localhost fromaddr: my_app@domain.tld toaddrs: - support_team@domain.tld - dev_team@domain.tld subject: Houston, we have a problem.
in the configuration, the string ``'cfg://handlers'`` would resolve to
the dict with key ``handlers``, the string ``'cfg://ha... | trusted_official_docs | CPython Docs | handlers: email: class: logging.handlers.SMTPHandler mailhost: localhost fromaddr: my_app@domain.tld toaddrs: - support_team@domain.tld - dev_team@domain.tld subject: Houston, we have a problem.
in the configuration, the string ``'cfg://handlers'`` would resolve to
the dict with key ``handlers``, the string ``'cfg://ha... | handlers: email: class: logging.handlers.SMTPHandler mailhost: localhost fromaddr: my_app@domain.tld toaddrs: - support_team@domain.tld - dev_team@domain.tld subject: Houston, we have a problem.
in the configuration, the string ``'cfg://handlers'`` would resolve to
the dict with key ``handlers``, the string ``'cfg://ha... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
59a8b885-0f7f-43be-b00a-13e30d972947 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,970 | supabase-export-v2 | bd69fa2fe43862ed | * A non-existent handler id found during an incremental call. * An invalid logger name. * Inability to resolve to an internal or external object.
Parsing is performed by the :class:`DictConfigurator` class, whose
constructor is passed the dictionary used for configuration, and
has a :meth:`configure` method. The :mod... | trusted_official_docs | CPython Docs | * A non-existent handler id found during an incremental call. * An invalid logger name. * Inability to resolve to an internal or external object.
Parsing is performed by the :class:`DictConfigurator` class, whose
constructor is passed the dictionary used for configuration, and
has a :meth:`configure` method. The :mod... | * A non-existent handler id found during an incremental call. * An invalid logger name. * Inability to resolve to an internal or external object.
Parsing is performed by the :class:`DictConfigurator` class, whose
constructor is passed the dictionary used for configuration, and
has a :meth:`configure` method. The :mod... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5c3ca798-58aa-499e-8045-600a746362c1 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,156 | supabase-export-v2 | 9692fc17c7a8786f | [formatter_form01] format=F1 %(asctime)s %(levelname)s %(message)s %(customfield)s datefmt= style=% validate=True defaults={'customfield': 'defaultvalue'} class=logging.Formatter
The arguments for the formatter configuration are the same as the keys
in the dictionary schema :ref:`formatters section
<logging-config-dict... | trusted_official_docs | CPython Docs | [formatter_form01] format=F1 %(asctime)s %(levelname)s %(message)s %(customfield)s datefmt= style=% validate=True defaults={'customfield': 'defaultvalue'} class=logging.Formatter
The arguments for the formatter configuration are the same as the keys
in the dictionary schema :ref:`formatters section
<logging-config-dict... | [formatter_form01] format=F1 %(asctime)s %(levelname)s %(message)s %(customfield)s datefmt= style=% validate=True defaults={'customfield': 'defaultvalue'} class=logging.Formatter
The arguments for the formatter configuration are the same as the keys
in the dictionary schema :ref:`formatters section
<logging-config-dict... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5caeaa5e-f4c8-4702-a18f-9482617792fc | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,094 | supabase-export-v2 | bffcd15505ddfe61 | Import resolution and custom importers """"""""""""""""""""""""""""""""""""""
Import resolution, by default, uses the builtin :func:`__import__` function
to do its importing. You may want to replace this with your own importing
mechanism: if so, you can replace the :attr:`importer` attribute of the
:class:`DictConfigur... | trusted_official_docs | CPython Docs | Import resolution and custom importers """"""""""""""""""""""""""""""""""""""
Import resolution, by default, uses the builtin :func:`__import__` function
to do its importing. You may want to replace this with your own importing
mechanism: if so, you can replace the :attr:`importer` attribute of the
:class:`DictConfigur... | Import resolution and custom importers """"""""""""""""""""""""""""""""""""""
Import resolution, by default, uses the builtin :func:`__import__` function
to do its importing. You may want to replace this with your own importing
mechanism: if so, you can replace the :attr:`importer` attribute of the
:class:`DictConfigur... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5cbd03a9-12b2-4660-ad1d-b777ffdd1bc0 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,979 | supabase-export-v2 | 6ae60614de06e8ea | method, it is assumed to be a file-like object and read using :meth:`~configparser.ConfigParser.read_file`; otherwise, it is assumed to be a filename and passed to :meth:`~configparser.ConfigParser.read`.
:param defaults: Defaults to be passed to the :class:`!ConfigParser` can be specified
in this argument. | trusted_official_docs | CPython Docs | method, it is assumed to be a file-like object and read using :meth:`~configparser.ConfigParser.read_file`; otherwise, it is assumed to be a filename and passed to :meth:`~configparser.ConfigParser.read`.
:param defaults: Defaults to be passed to the :class:`!ConfigParser` can be specified
in this argument. | method, it is assumed to be a file-like object and read using :meth:`~configparser.ConfigParser.read_file`; otherwise, it is assumed to be a filename and passed to :meth:`~configparser.ConfigParser.read`.
:param defaults: Defaults to be passed to the :class:`!ConfigParser` can be specified
in this argument. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5cc193c9-bf92-4360-a93e-910d66addfe6 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,109 | supabase-export-v2 | 20895037edd0bdcb | with a ``'()'`` key which is constructed in the usual way as discussed in :ref:`logging-config-dict-userdef`. The result of this construction should be a :class:`queue.Queue` instance.
If the ``queue`` key is absent, a standard unbounded :class:`queue.Queue` instance is
created and used. | trusted_official_docs | CPython Docs | with a ``'()'`` key which is constructed in the usual way as discussed in :ref:`logging-config-dict-userdef`. The result of this construction should be a :class:`queue.Queue` instance.
If the ``queue`` key is absent, a standard unbounded :class:`queue.Queue` instance is
created and used. | with a ``'()'`` key which is constructed in the usual way as discussed in :ref:`logging-config-dict-userdef`. The result of this construction should be a :class:`queue.Queue` instance.
If the ``queue`` key is absent, a standard unbounded :class:`queue.Queue` instance is
created and used. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5d033500-2104-4569-b525-1da9752462be | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,059 | supabase-export-v2 | 25db3ef53ef1eaed | and will result in a :class:`logging.Formatter` initialized with those two format strings. Shown in Python source form, the ``brief`` and ``default`` formatters have configuration sub-dictionaries::
{
'format' : '%(message)s'
} | trusted_official_docs | CPython Docs | and will result in a :class:`logging.Formatter` initialized with those two format strings. Shown in Python source form, the ``brief`` and ``default`` formatters have configuration sub-dictionaries::
{
'format' : '%(message)s'
} | and will result in a :class:`logging.Formatter` initialized with those two format strings. Shown in Python source form, the ``brief`` and ``default`` formatters have configuration sub-dictionaries::
{
'format' : '%(message)s'
} | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5d2200a4-0000-43fc-b854-18384b90365f | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,068 | supabase-export-v2 | c2e867f1f8f17257 | .. versionchanged:: 3.11 The ``filters`` member of ``handlers`` and ``loggers`` can take filter instances in addition to ids.
You can also specify a special key ``'.'`` whose value is a
mapping of attribute names to values. If found, the specified attributes will
be set on the user-defined object before it is returned.... | trusted_official_docs | CPython Docs | .. versionchanged:: 3.11 The ``filters`` member of ``handlers`` and ``loggers`` can take filter instances in addition to ids.
You can also specify a special key ``'.'`` whose value is a
mapping of attribute names to values. If found, the specified attributes will
be set on the user-defined object before it is returned.... | .. versionchanged:: 3.11 The ``filters`` member of ``handlers`` and ``loggers`` can take filter instances in addition to ids.
You can also specify a special key ``'.'`` whose value is a
mapping of attribute names to values. If found, the specified attributes will
be set on the user-defined object before it is returned.... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5d6c8947-f0db-4175-b9b9-ef3db90008a3 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,984 | supabase-export-v2 | 749222daba6f7d9d | file, and then modified by the using application (e.g. based on command-line parameters or other aspects of the runtime environment) before being passed to ``fileConfig``.
.. versionchanged:: 3.10
Added the *encoding* parameter. | trusted_official_docs | CPython Docs | file, and then modified by the using application (e.g. based on command-line parameters or other aspects of the runtime environment) before being passed to ``fileConfig``.
.. versionchanged:: 3.10
Added the *encoding* parameter. | file, and then modified by the using application (e.g. based on command-line parameters or other aspects of the runtime environment) before being passed to ``fileConfig``.
.. versionchanged:: 3.10
Added the *encoding* parameter. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5df78ce1-2c41-4e2c-9bdd-9152eb59d22b | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,980 | supabase-export-v2 | df5376511b01059b | :param defaults: Defaults to be passed to the :class:`!ConfigParser` can be specified in this argument.
:param disable_existing_loggers: If specified as ``False``, loggers which
exist when this call is made are left
enabled. The default is ``True`` because this
enables old behaviour in a
backward-compatible way. Th... | trusted_official_docs | CPython Docs | :param defaults: Defaults to be passed to the :class:`!ConfigParser` can be specified in this argument.
:param disable_existing_loggers: If specified as ``False``, loggers which
exist when this call is made are left
enabled. The default is ``True`` because this
enables old behaviour in a
backward-compatible way. Th... | :param defaults: Defaults to be passed to the :class:`!ConfigParser` can be specified in this argument.
:param disable_existing_loggers: If specified as ``False``, loggers which
exist when this call is made are left
enabled. The default is ``True`` because this
enables old behaviour in a
backward-compatible way. Th... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
5e0ca493-f856-42fb-ac2c-bd528df63827 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,033 | supabase-export-v2 | 8a0bd7ecd11bbe17 | The specified loggers will be configured according to the level, propagation, filters and handlers specified.
* *root* - this will be the configuration for the root logger. Processing of the configuration will be as for any logger, except
that the ``propagate`` setting will not be applicable. | trusted_official_docs | CPython Docs | The specified loggers will be configured according to the level, propagation, filters and handlers specified.
* *root* - this will be the configuration for the root logger. Processing of the configuration will be as for any logger, except
that the ``propagate`` setting will not be applicable. | The specified loggers will be configured according to the level, propagation, filters and handlers specified.
* *root* - this will be the configuration for the root logger. Processing of the configuration will be as for any logger, except
that the ``propagate`` setting will not be applicable. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
60837307-fd23-4755-8831-a2fa48488e3c | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,014 | supabase-export-v2 | 8cab78ddabfebc15 | The configuring dict is searched for the key ``name`` (defaulting to the empty string) and this is used to construct a :class:`logging.Filter` instance.
* *handlers* - the corresponding value will be a dict in which each
key is a handler id and each value is a dict describing how to
configure the corresponding Handle... | trusted_official_docs | CPython Docs | The configuring dict is searched for the key ``name`` (defaulting to the empty string) and this is used to construct a :class:`logging.Filter` instance.
* *handlers* - the corresponding value will be a dict in which each
key is a handler id and each value is a dict describing how to
configure the corresponding Handle... | The configuring dict is searched for the key ``name`` (defaulting to the empty string) and this is used to construct a :class:`logging.Filter` instance.
* *handlers* - the corresponding value will be a dict in which each
key is a handler id and each value is a dict describing how to
configure the corresponding Handle... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
6cbcc548-09b3-471f-906a-b5c3921b6225 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,061 | supabase-export-v2 | 5003674d2cf4d1cf | { 'format' : '%(asctime)s %(levelname)-8s %(name)-15s %(message)s', 'datefmt' : '%Y-%m-%d %H:%M:%S' }
respectively, and as these dictionaries do not contain the special key
``'()'``, the instantiation is inferred from the context: as a result,
standard :class:`logging.Formatter` instances are created. The
configuration... | trusted_official_docs | CPython Docs | { 'format' : '%(asctime)s %(levelname)-8s %(name)-15s %(message)s', 'datefmt' : '%Y-%m-%d %H:%M:%S' }
respectively, and as these dictionaries do not contain the special key
``'()'``, the instantiation is inferred from the context: as a result,
standard :class:`logging.Formatter` instances are created. The
configuration... | { 'format' : '%(asctime)s %(levelname)-8s %(name)-15s %(message)s', 'datefmt' : '%Y-%m-%d %H:%M:%S' }
respectively, and as these dictionaries do not contain the special key
``'()'``, the instantiation is inferred from the context: as a result,
standard :class:`logging.Formatter` instances are created. The
configuration... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
6e03d8dc-c48a-4401-a612-abb230e64fc5 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,995 | supabase-export-v2 | 86a7523f7d3cd847 | .. note::
If you want to send configurations to the listener which don't
disable existing loggers, you will need to use a JSON format for
the configuration, which will use :func:`dictConfig` for configuration. This method allows you to specify ``disable_existing_loggers`` as
``False`` in the configuration you send. | trusted_official_docs | CPython Docs | .. note::
If you want to send configurations to the listener which don't
disable existing loggers, you will need to use a JSON format for
the configuration, which will use :func:`dictConfig` for configuration. This method allows you to specify ``disable_existing_loggers`` as
``False`` in the configuration you send. | .. note::
If you want to send configurations to the listener which don't
disable existing loggers, you will need to use a JSON format for
the configuration, which will use :func:`dictConfig` for configuration. This method allows you to specify ``disable_existing_loggers`` as
``False`` in the configuration you send. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
6e83eaf9-e53f-40f9-83f1-ba8470ca6bb4 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,137 | supabase-export-v2 | 3b8962d50a6b8a8a | The ``qualname`` entry is the hierarchical channel name of the logger, that is to say the name used by the application to get the logger.
Sections which specify handler configuration are exemplified by the following. | trusted_official_docs | CPython Docs | The ``qualname`` entry is the hierarchical channel name of the logger, that is to say the name used by the application to get the logger.
Sections which specify handler configuration are exemplified by the following. | The ``qualname`` entry is the hierarchical channel name of the logger, that is to say the name used by the application to get the logger.
Sections which specify handler configuration are exemplified by the following. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
6f572e20-4967-4ced-92f4-0ba3444615db | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,075 | supabase-export-v2 | 6a68b76c4dd208d3 | are configured *after* any handlers they depend on; that allows something like ``cfg://handlers.foo`` to be used in configuring a handler that depends on handler ``foo``.
If that dependent handler were named ``bar``,
problems would result, because the configuration of ``bar`` would be attempted
before that of ``foo``, ... | trusted_official_docs | CPython Docs | are configured *after* any handlers they depend on; that allows something like ``cfg://handlers.foo`` to be used in configuring a handler that depends on handler ``foo``.
If that dependent handler were named ``bar``,
problems would result, because the configuration of ``bar`` would be attempted
before that of ``foo``, ... | are configured *after* any handlers they depend on; that allows something like ``cfg://handlers.foo`` to be used in configuring a handler that depends on handler ``foo``.
If that dependent handler were named ``bar``,
problems would result, because the configuration of ``bar`` would be attempted
before that of ``foo``, ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
701be258-899d-42d9-8bc8-1d3f00addebf | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,991 | supabase-export-v2 | 9015c42266e1f3f1 | .. note::
Because portions of the configuration are passed through
:func:`eval`, use of this function may open its users to a security risk. While the function only binds to a socket on ``localhost``, and so does
not accept connections from remote machines, there are scenarios where
untrusted code could be run under... | trusted_official_docs | CPython Docs | .. note::
Because portions of the configuration are passed through
:func:`eval`, use of this function may open its users to a security risk. While the function only binds to a socket on ``localhost``, and so does
not accept connections from remote machines, there are scenarios where
untrusted code could be run under... | .. note::
Because portions of the configuration are passed through
:func:`eval`, use of this function may open its users to a security risk. While the function only binds to a socket on ``localhost``, and so does
not accept connections from remote machines, there are scenarios where
untrusted code could be run under... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
738c520d-b8b3-48f8-acb8-7bd36d74ba1c | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,143 | supabase-export-v2 | 3647c8af347a30e7 | the constructors for the relevant handlers, or to the examples below, to see how typical entries are constructed. If not provided, it defaults to ``()``.
The optional ``kwargs`` entry, when :ref:`evaluated <func-eval>` in the context of the
``logging`` package's namespace, is the keyword argument dict to the constructo... | trusted_official_docs | CPython Docs | the constructors for the relevant handlers, or to the examples below, to see how typical entries are constructed. If not provided, it defaults to ``()``.
The optional ``kwargs`` entry, when :ref:`evaluated <func-eval>` in the context of the
``logging`` package's namespace, is the keyword argument dict to the constructo... | the constructors for the relevant handlers, or to the examples below, to see how typical entries are constructed. If not provided, it defaults to ``()``.
The optional ``kwargs`` entry, when :ref:`evaluated <func-eval>` in the context of the
``logging`` package's namespace, is the keyword argument dict to the constructo... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
73a78c9b-e415-4da5-a00e-6585a9c52d56 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,062 | supabase-export-v2 | d18262175c1d6dca | instantiation is inferred from the context: as a result, standard :class:`logging.Formatter` instances are created. The configuration sub-dictionary for the third formatter, with id ``custom``, is::
{
'()' : 'my.package.customFormatterFactory',
'bar' : 'baz',
'spam' : 99.9,
'answer' : 42
} | trusted_official_docs | CPython Docs | instantiation is inferred from the context: as a result, standard :class:`logging.Formatter` instances are created. The configuration sub-dictionary for the third formatter, with id ``custom``, is::
{
'()' : 'my.package.customFormatterFactory',
'bar' : 'baz',
'spam' : 99.9,
'answer' : 42
} | instantiation is inferred from the context: as a result, standard :class:`logging.Formatter` instances are created. The configuration sub-dictionary for the third formatter, with id ``custom``, is::
{
'()' : 'my.package.customFormatterFactory',
'bar' : 'baz',
'spam' : 99.9,
'answer' : 42
} | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
75f75390-7f2b-4186-97ee-6a77c57947e4 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,036 | supabase-export-v2 | 4290420593c5b998 | If the specified value is ``True``, the configuration is processed as described in the section on :ref:`logging-config-dict-incremental`.
* *disable_existing_loggers* - whether any existing non-root loggers are
to be disabled. This setting mirrors the parameter of the same name in
:func:`fileConfig`. If absent, this ... | trusted_official_docs | CPython Docs | If the specified value is ``True``, the configuration is processed as described in the section on :ref:`logging-config-dict-incremental`.
* *disable_existing_loggers* - whether any existing non-root loggers are
to be disabled. This setting mirrors the parameter of the same name in
:func:`fileConfig`. If absent, this ... | If the specified value is ``True``, the configuration is processed as described in the section on :ref:`logging-config-dict-incremental`.
* *disable_existing_loggers* - whether any existing non-root loggers are
to be disabled. This setting mirrors the parameter of the same name in
:func:`fileConfig`. If absent, this ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
79111969-0efa-4dab-8cfe-a2c8172362a8 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,087 | supabase-export-v2 | 044e4046ecd4de4b | custom: (): my.package.MyHandler alternate: cfg://handlers.file
The literal string ``'cfg://handlers.file'`` will be resolved in an
analogous way to strings with the ``ext://`` prefix, but looking
in the configuration itself rather than the import namespace. The
mechanism allows access by dot or by index, in a similar ... | trusted_official_docs | CPython Docs | custom: (): my.package.MyHandler alternate: cfg://handlers.file
The literal string ``'cfg://handlers.file'`` will be resolved in an
analogous way to strings with the ``ext://`` prefix, but looking
in the configuration itself rather than the import namespace. The
mechanism allows access by dot or by index, in a similar ... | custom: (): my.package.MyHandler alternate: cfg://handlers.file
The literal string ``'cfg://handlers.file'`` will be resolved in an
analogous way to strings with the ``ext://`` prefix, but looking
in the configuration itself rather than the import namespace. The
mechanism allows access by dot or by index, in a similar ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
81db3efb-ff10-4b41-b4fe-c2ecfc3495b3 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,110 | supabase-export-v2 | a64a88382cf51f52 | If the ``queue`` key is absent, a standard unbounded :class:`queue.Queue` instance is created and used.
If the ``listener`` key is present, the corresponding value can be one of the following: | trusted_official_docs | CPython Docs | If the ``queue`` key is absent, a standard unbounded :class:`queue.Queue` instance is created and used.
If the ``listener`` key is present, the corresponding value can be one of the following: | If the ``queue`` key is absent, a standard unbounded :class:`queue.Queue` instance is created and used.
If the ``listener`` key is present, the corresponding value can be one of the following: | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
841412ed-0e71-4d0d-90b1-733504b86008 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,978 | supabase-export-v2 | f8e09af936bb6ccf | It will raise :exc:`FileNotFoundError` if the file doesn't exist and :exc:`RuntimeError` if the file is invalid or empty.
:param fname: A filename, or a file-like object, or an instance derived
from :class:`~configparser.RawConfigParser`. If a
:class:`!RawConfigParser`-derived instance is passed, it is used as
is. O... | trusted_official_docs | CPython Docs | It will raise :exc:`FileNotFoundError` if the file doesn't exist and :exc:`RuntimeError` if the file is invalid or empty.
:param fname: A filename, or a file-like object, or an instance derived
from :class:`~configparser.RawConfigParser`. If a
:class:`!RawConfigParser`-derived instance is passed, it is used as
is. O... | It will raise :exc:`FileNotFoundError` if the file doesn't exist and :exc:`RuntimeError` if the file is invalid or empty.
:param fname: A filename, or a file-like object, or an instance derived
from :class:`~configparser.RawConfigParser`. If a
:class:`!RawConfigParser`-derived instance is passed, it is used as
is. O... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
86a0d7bd-9431-4ac2-b1e8-13610afad735 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,091 | supabase-export-v2 | dbe5d7a42b808e12 | an index value consists only of decimal digits, access will be attempted using the corresponding integer value, falling back to the string value if needed.
Given a string ``cfg://handlers.myhandler.mykey.123``, this will
resolve to ``config_dict['handlers']['myhandler']['mykey']['123']``. If the string is specified as ... | trusted_official_docs | CPython Docs | an index value consists only of decimal digits, access will be attempted using the corresponding integer value, falling back to the string value if needed.
Given a string ``cfg://handlers.myhandler.mykey.123``, this will
resolve to ``config_dict['handlers']['myhandler']['mykey']['123']``. If the string is specified as ... | an index value consists only of decimal digits, access will be attempted using the corresponding integer value, falling back to the string value if needed.
Given a string ``cfg://handlers.myhandler.mykey.123``, this will
resolve to ``config_dict['handlers']['myhandler']['mykey']['123']``. If the string is specified as ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
87bdd98a-8e5a-4e25-be25-f9e78579a1e9 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,999 | supabase-export-v2 | e5a8754e2d72e628 | Security considerations ^^^^^^^^^^^^^^^^^^^^^^^
The logging configuration functionality tries to offer convenience, and in part this
is done by offering the ability to convert text in configuration files into Python
objects used in logging configuration - for example, as described in
:ref:`logging-config-dict-userdef`.... | trusted_official_docs | CPython Docs | Security considerations ^^^^^^^^^^^^^^^^^^^^^^^
The logging configuration functionality tries to offer convenience, and in part this
is done by offering the ability to convert text in configuration files into Python
objects used in logging configuration - for example, as described in
:ref:`logging-config-dict-userdef`.... | Security considerations ^^^^^^^^^^^^^^^^^^^^^^^
The logging configuration functionality tries to offer convenience, and in part this
is done by offering the ability to convert text in configuration files into Python
objects used in logging configuration - for example, as described in
:ref:`logging-config-dict-userdef`.... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
87d2120b-d496-44c2-ba59-aedbb273ef33 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,981 | supabase-export-v2 | ddbf2c7d52bc3264 | in a backward-compatible way. This behaviour is to disable any existing non-root loggers unless they or their ancestors are explicitly named in the logging configuration.
:param encoding: The encoding used to open file when *fname* is filename. | trusted_official_docs | CPython Docs | in a backward-compatible way. This behaviour is to disable any existing non-root loggers unless they or their ancestors are explicitly named in the logging configuration.
:param encoding: The encoding used to open file when *fname* is filename. | in a backward-compatible way. This behaviour is to disable any existing non-root loggers unless they or their ancestors are explicitly named in the logging configuration.
:param encoding: The encoding used to open file when *fname* is filename. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
87e19f55-5fc5-4055-adfa-33fecae88575 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,140 | supabase-export-v2 | ad79572c49597fe8 | [handler_hand01] class=StreamHandler level=NOTSET formatter=form01 args=(sys.stdout,)
The ``class`` entry indicates the handler's class (as determined by :func:`eval`
in the ``logging`` package's namespace). The ``level`` is interpreted as for
loggers, and ``NOTSET`` is taken to mean 'log everything'. | trusted_official_docs | CPython Docs | [handler_hand01] class=StreamHandler level=NOTSET formatter=form01 args=(sys.stdout,)
The ``class`` entry indicates the handler's class (as determined by :func:`eval`
in the ``logging`` package's namespace). The ``level`` is interpreted as for
loggers, and ``NOTSET`` is taken to mean 'log everything'. | [handler_hand01] class=StreamHandler level=NOTSET formatter=form01 args=(sys.stdout,)
The ``class`` entry indicates the handler's class (as determined by :func:`eval`
in the ``logging`` package's namespace). The ``level`` is interpreted as for
loggers, and ``NOTSET`` is taken to mean 'log everything'. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
899f12db-af6f-497d-83ee-20967eaafb5e | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,111 | supabase-export-v2 | 090c0348b166485e | If the ``listener`` key is present, the corresponding value can be one of the following:
* A subclass of :class:`logging.handlers.QueueListener`. This is of course only
possible if you are constructing or modifying the configuration dictionary in
code. | trusted_official_docs | CPython Docs | If the ``listener`` key is present, the corresponding value can be one of the following:
* A subclass of :class:`logging.handlers.QueueListener`. This is of course only
possible if you are constructing or modifying the configuration dictionary in
code. | If the ``listener`` key is present, the corresponding value can be one of the following:
* A subclass of :class:`logging.handlers.QueueListener`. This is of course only
possible if you are constructing or modifying the configuration dictionary in
code. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
8cb12953-27ce-4a91-aca2-2d4770ed3902 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,078 | supabase-export-v2 | ceda817ed0f5d6ee | Access to external objects """"""""""""""""""""""""""
There are times where a configuration needs to refer to objects
external to the configuration, for example ``sys.stderr``. If the
configuration dict is constructed using Python code, this is
straightforward, but a problem arises when the configuration is
provided vi... | trusted_official_docs | CPython Docs | Access to external objects """"""""""""""""""""""""""
There are times where a configuration needs to refer to objects
external to the configuration, for example ``sys.stderr``. If the
configuration dict is constructed using Python code, this is
straightforward, but a problem arises when the configuration is
provided vi... | Access to external objects """"""""""""""""""""""""""
There are times where a configuration needs to refer to objects
external to the configuration, for example ``sys.stderr``. If the
configuration dict is constructed using Python code, this is
straightforward, but a problem arises when the configuration is
provided vi... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
8e72208b-4f6b-4846-a073-8496b8500f38 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,051 | supabase-export-v2 | aeb9db17c2bdbb2c | only meaningful for processing the configuration dictionary and used to determine connections between objects, and are not persisted anywhere when the configuration call is complete.
The above snippet indicates that logger named ``foo.bar.baz`` should
have two handlers attached to it, which are described by the handler... | trusted_official_docs | CPython Docs | only meaningful for processing the configuration dictionary and used to determine connections between objects, and are not persisted anywhere when the configuration call is complete.
The above snippet indicates that logger named ``foo.bar.baz`` should
have two handlers attached to it, which are described by the handler... | only meaningful for processing the configuration dictionary and used to determine connections between objects, and are not persisted anywhere when the configuration call is complete.
The above snippet indicates that logger named ``foo.bar.baz`` should
have two handlers attached to it, which are described by the handler... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
8eae802f-3d48-42bf-a383-55f21710c651 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,034 | supabase-export-v2 | 0a10d7e3c572a539 | the configuration for the root logger. Processing of the configuration will be as for any logger, except that the ``propagate`` setting will not be applicable.
* *incremental* - whether the configuration is to be interpreted as
incremental to the existing configuration. This value defaults to
``False``, which means t... | trusted_official_docs | CPython Docs | the configuration for the root logger. Processing of the configuration will be as for any logger, except that the ``propagate`` setting will not be applicable.
* *incremental* - whether the configuration is to be interpreted as
incremental to the existing configuration. This value defaults to
``False``, which means t... | the configuration for the root logger. Processing of the configuration will be as for any logger, except that the ``propagate`` setting will not be applicable.
* *incremental* - whether the configuration is to be interpreted as
incremental to the existing configuration. This value defaults to
``False``, which means t... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
91783ed6-7109-4884-91b3-28b43e05df09 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,095 | supabase-export-v2 | d240e2fa5ffd9338 | do your imports, and you want to define it at class level rather than instance level, you need to wrap it with :func:`staticmethod`. For example::
from importlib import import_module
from logging.config import BaseConfigurator | trusted_official_docs | CPython Docs | do your imports, and you want to define it at class level rather than instance level, you need to wrap it with :func:`staticmethod`. For example::
from importlib import import_module
from logging.config import BaseConfigurator | do your imports, and you want to define it at class level rather than instance level, you need to wrap it with :func:`staticmethod`. For example::
from importlib import import_module
from logging.config import BaseConfigurator | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
962a75fb-2729-4e81-aa40-d1227532b6ca | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,045 | supabase-export-v2 | 10b91fdc8a923edf | Object connections """"""""""""""""""
The schema describes a set of logging objects - loggers,
handlers, formatters, filters - which are connected to each other in
an object graph. Thus, the schema needs to represent connections
between the objects. For example, say that, once configured, a
particular logger has attach... | trusted_official_docs | CPython Docs | Object connections """"""""""""""""""
The schema describes a set of logging objects - loggers,
handlers, formatters, filters - which are connected to each other in
an object graph. Thus, the schema needs to represent connections
between the objects. For example, say that, once configured, a
particular logger has attach... | Object connections """"""""""""""""""
The schema describes a set of logging objects - loggers,
handlers, formatters, filters - which are connected to each other in
an object graph. Thus, the schema needs to represent connections
between the objects. For example, say that, once configured, a
particular logger has attach... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
97627243-5f81-4d19-b392-9c8da3156cd8 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,046 | supabase-export-v2 | c065550a007aa7ec | then using the id in the source object's configuration to indicate that a connection exists between the source and the destination object with that id.
So, for example, consider the following YAML snippet: | trusted_official_docs | CPython Docs | then using the id in the source object's configuration to indicate that a connection exists between the source and the destination object with that id.
So, for example, consider the following YAML snippet: | then using the id in the source object's configuration to indicate that a connection exists between the source and the destination object with that id.
So, for example, consider the following YAML snippet: | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
9b68dbf7-913a-4cc3-ba04-fc78f368a249 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,142 | supabase-export-v2 | 6c96f69aa8ea83f4 | formatter (``logging._defaultFormatter``) is used. If a name is specified, it must appear in the ``[formatters]`` section and have a corresponding section in the configuration file.
The ``args`` entry, when :ref:`evaluated <func-eval>` in the context of the ``logging``
package's namespace, is the list of arguments to t... | trusted_official_docs | CPython Docs | formatter (``logging._defaultFormatter``) is used. If a name is specified, it must appear in the ``[formatters]`` section and have a corresponding section in the configuration file.
The ``args`` entry, when :ref:`evaluated <func-eval>` in the context of the ``logging``
package's namespace, is the list of arguments to t... | formatter (``logging._defaultFormatter``) is used. If a name is specified, it must appear in the ``[formatters]`` section and have a corresponding section in the configuration file.
The ``args`` entry, when :ref:`evaluated <func-eval>` in the context of the ``logging``
package's namespace, is the list of arguments to t... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
9eb7d374-98cc-4184-8341-d333cae07ecd | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,048 | supabase-export-v2 | 7d4144cc084cdfd9 | .. code-block:: yaml
formatters:
brief:
# configuration for formatter with id 'brief' goes here
precise:
# configuration for formatter with id 'precise' goes here
handlers:
h1: #This is an id
# configuration of handler with id 'h1' goes here
formatter: brief
h2: #This is another id
# configuration of handler ... | trusted_official_docs | CPython Docs | .. code-block:: yaml
formatters:
brief:
# configuration for formatter with id 'brief' goes here
precise:
# configuration for formatter with id 'precise' goes here
handlers:
h1: #This is an id
# configuration of handler with id 'h1' goes here
formatter: brief
h2: #This is another id
# configuration of handler ... | .. code-block:: yaml
formatters:
brief:
# configuration for formatter with id 'brief' goes here
precise:
# configuration for formatter with id 'precise' goes here
handlers:
h1: #This is an id
# configuration of handler with id 'h1' goes here
formatter: brief
h2: #This is another id
# configuration of handler ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
9fe51858-e4ae-482b-be4f-f145551b16cc | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,054 | supabase-export-v2 | 99b6a1980013efa2 | User-defined objects """"""""""""""""""""
The schema supports user-defined objects for handlers, filters and
formatters. (Loggers do not need to have different types for
different instances, so there is no support in this configuration
schema for user-defined logger classes.) | trusted_official_docs | CPython Docs | User-defined objects """"""""""""""""""""
The schema supports user-defined objects for handlers, filters and
formatters. (Loggers do not need to have different types for
different instances, so there is no support in this configuration
schema for user-defined logger classes.) | User-defined objects """"""""""""""""""""
The schema supports user-defined objects for handlers, filters and
formatters. (Loggers do not need to have different types for
different instances, so there is no support in this configuration
schema for user-defined logger classes.) | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
a047253e-fde3-4477-8f21-2b966ed8ecbc | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,025 | supabase-export-v2 | 8442583d3d169a87 | a :class:`logging.StreamHandler`, using ``sys.stdout`` as the underlying stream. The handler with id ``file`` is instantiated as a :class:`logging.handlers.RotatingFileHandler` with the keyword arguments ``filename='logconfig.log', maxBytes=1024, backupCount=3``.
* *loggers* - the corresponding value will be a dict in ... | trusted_official_docs | CPython Docs | a :class:`logging.StreamHandler`, using ``sys.stdout`` as the underlying stream. The handler with id ``file`` is instantiated as a :class:`logging.handlers.RotatingFileHandler` with the keyword arguments ``filename='logconfig.log', maxBytes=1024, backupCount=3``.
* *loggers* - the corresponding value will be a dict in ... | a :class:`logging.StreamHandler`, using ``sys.stdout`` as the underlying stream. The handler with id ``file`` is instantiated as a :class:`logging.handlers.RotatingFileHandler` with the keyword arguments ``filename='logconfig.log', maxBytes=1024, backupCount=3``.
* *loggers* - the corresponding value will be a dict in ... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
a621356a-7e68-4a9d-8763-a03a856cfbd7 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,015 | supabase-export-v2 | a0c0e152a949a4a2 | be a dict in which each key is a handler id and each value is a dict describing how to configure the corresponding Handler instance.
The configuring dict is searched for the following keys: | trusted_official_docs | CPython Docs | be a dict in which each key is a handler id and each value is a dict describing how to configure the corresponding Handler instance.
The configuring dict is searched for the following keys: | be a dict in which each key is a handler id and each value is a dict describing how to configure the corresponding Handler instance.
The configuring dict is searched for the following keys: | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
ab0c1a65-fc03-4508-9cf6-4f186c9a1e7f | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,005 | supabase-export-v2 | e2182c33c5d28681 | The dictionary passed to :func:`dictConfig` must contain the following keys:
* *version* - to be set to an integer value representing the schema
version. The only valid value at present is 1, but having this key
allows the schema to evolve while still preserving backwards
compatibility. | trusted_official_docs | CPython Docs | The dictionary passed to :func:`dictConfig` must contain the following keys:
* *version* - to be set to an integer value representing the schema
version. The only valid value at present is 1, but having this key
allows the schema to evolve while still preserving backwards
compatibility. | The dictionary passed to :func:`dictConfig` must contain the following keys:
* *version* - to be set to an integer value representing the schema
version. The only valid value at present is 1, but having this key
allows the schema to evolve while still preserving backwards
compatibility. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
ac518355-ec73-4777-b454-85acb58c4634 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,983 | supabase-export-v2 | d780d2a087738024 | .. versionchanged:: 3.4 An instance of a subclass of :class:`~configparser.RawConfigParser` is now accepted as a value for ``fname``. This facilitates:
* Use of a configuration file where logging configuration is just part
of the overall application configuration. * Use of a configuration read from a file, and then mo... | trusted_official_docs | CPython Docs | .. versionchanged:: 3.4 An instance of a subclass of :class:`~configparser.RawConfigParser` is now accepted as a value for ``fname``. This facilitates:
* Use of a configuration file where logging configuration is just part
of the overall application configuration. * Use of a configuration read from a file, and then mo... | .. versionchanged:: 3.4 An instance of a subclass of :class:`~configparser.RawConfigParser` is now accepted as a value for ``fname``. This facilitates:
* Use of a configuration file where logging configuration is just part
of the overall application configuration. * Use of a configuration read from a file, and then mo... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
ad82d038-ecee-4a17-badd-723fa7b127e7 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,993 | supabase-export-v2 | 9e5244b9a70b9e41 | a different port is used. To avoid the risk of this happening, use the ``verify`` argument to :func:`listen` to prevent unrecognised configurations from being applied.
.. versionchanged:: 3.4
The ``verify`` argument was added. | trusted_official_docs | CPython Docs | a different port is used. To avoid the risk of this happening, use the ``verify`` argument to :func:`listen` to prevent unrecognised configurations from being applied.
.. versionchanged:: 3.4
The ``verify`` argument was added. | a different port is used. To avoid the risk of this happening, use the ``verify`` argument to :func:`listen` to prevent unrecognised configurations from being applied.
.. versionchanged:: 3.4
The ``verify`` argument was added. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
ada1a5d2-bbc6-4f3e-85ea-b49958de84f7 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,010 | supabase-export-v2 | e8b350f4badf4131 | The configuring dict is searched for the following optional keys which correspond to the arguments passed to create a :class:`~logging.Formatter` object:
* ``format``
* ``datefmt``
* ``style``
* ``validate`` (since version >=3.8)
* ``defaults`` (since version >=3.12) | trusted_official_docs | CPython Docs | The configuring dict is searched for the following optional keys which correspond to the arguments passed to create a :class:`~logging.Formatter` object:
* ``format``
* ``datefmt``
* ``style``
* ``validate`` (since version >=3.8)
* ``defaults`` (since version >=3.12) | The configuring dict is searched for the following optional keys which correspond to the arguments passed to create a :class:`~logging.Formatter` object:
* ``format``
* ``datefmt``
* ``style``
* ``validate`` (since version >=3.8)
* ``defaults`` (since version >=3.12) | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
b6431d4e-d39c-4200-b700-2956dc16a894 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,082 | supabase-export-v2 | ff935acb84d28096 | Access to internal objects """"""""""""""""""""""""""
As well as external objects, there is sometimes also a need to refer
to objects in the configuration. This will be done implicitly by the
configuration system for things that it knows about. For example, the
string value ``'DEBUG'`` for a ``level`` in a logger or ha... | trusted_official_docs | CPython Docs | Access to internal objects """"""""""""""""""""""""""
As well as external objects, there is sometimes also a need to refer
to objects in the configuration. This will be done implicitly by the
configuration system for things that it knows about. For example, the
string value ``'DEBUG'`` for a ``level`` in a logger or ha... | Access to internal objects """"""""""""""""""""""""""
As well as external objects, there is sometimes also a need to refer
to objects in the configuration. This will be done implicitly by the
configuration system for things that it knows about. For example, the
string value ``'DEBUG'`` for a ``level`` in a logger or ha... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
b81da53c-1265-4290-8926-8ea8ae6a23cb | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,987 | supabase-export-v2 | 05ba134dd764fa80 | .. function:: listen(port=DEFAULT_LOGGING_CONFIG_PORT, verify=None)
Starts up a socket server on the specified port, and listens for new
configurations. If no port is specified, the module's default
:const:`DEFAULT_LOGGING_CONFIG_PORT` is used. Logging configurations will be
sent as a file suitable for processing by... | trusted_official_docs | CPython Docs | .. function:: listen(port=DEFAULT_LOGGING_CONFIG_PORT, verify=None)
Starts up a socket server on the specified port, and listens for new
configurations. If no port is specified, the module's default
:const:`DEFAULT_LOGGING_CONFIG_PORT` is used. Logging configurations will be
sent as a file suitable for processing by... | .. function:: listen(port=DEFAULT_LOGGING_CONFIG_PORT, verify=None)
Starts up a socket server on the specified port, and listens for new
configurations. If no port is specified, the module's default
:const:`DEFAULT_LOGGING_CONFIG_PORT` is used. Logging configurations will be
sent as a file suitable for processing by... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
b88b6f65-6c27-4f96-99cf-dd6c35d32ec3 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,112 | supabase-export-v2 | f1f5ee8352a09562 | * A subclass of :class:`logging.handlers.QueueListener`. This is of course only possible if you are constructing or modifying the configuration dictionary in code.
* A string which resolves to a class which is a subclass of ``QueueListener``, such as
``'my.package.CustomListener'``. | trusted_official_docs | CPython Docs | * A subclass of :class:`logging.handlers.QueueListener`. This is of course only possible if you are constructing or modifying the configuration dictionary in code.
* A string which resolves to a class which is a subclass of ``QueueListener``, such as
``'my.package.CustomListener'``. | * A subclass of :class:`logging.handlers.QueueListener`. This is of course only possible if you are constructing or modifying the configuration dictionary in code.
* A string which resolves to a class which is a subclass of ``QueueListener``, such as
``'my.package.CustomListener'``. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
b8a3e6d1-b087-4560-b64e-206217ec6e94 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,159 | supabase-export-v2 | 71a091c393f76481 | .. note::
Due to the use of :func:`eval` as described above, there are
potential security risks which result from using the :func:`listen` to send
and receive configurations via sockets. The risks are limited to where
multiple users with no mutual trust run code on the same machine; see the
:func:`listen` documenta... | trusted_official_docs | CPython Docs | .. note::
Due to the use of :func:`eval` as described above, there are
potential security risks which result from using the :func:`listen` to send
and receive configurations via sockets. The risks are limited to where
multiple users with no mutual trust run code on the same machine; see the
:func:`listen` documenta... | .. note::
Due to the use of :func:`eval` as described above, there are
potential security risks which result from using the :func:`listen` to send
and receive configurations via sockets. The risks are limited to where
multiple users with no mutual trust run code on the same machine; see the
:func:`listen` documenta... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
b8b22c18-36de-4333-a110-760274caefb0 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,008 | supabase-export-v2 | 013ccde61c57b55e | .. _logging-config-dictschema-formatters:
* *formatters* - the corresponding value will be a dict in which each
key is a formatter id and each value is a dict describing how to
configure the corresponding :class:`~logging.Formatter` instance. | trusted_official_docs | CPython Docs | .. _logging-config-dictschema-formatters:
* *formatters* - the corresponding value will be a dict in which each
key is a formatter id and each value is a dict describing how to
configure the corresponding :class:`~logging.Formatter` instance. | .. _logging-config-dictschema-formatters:
* *formatters* - the corresponding value will be a dict in which each
key is a formatter id and each value is a dict describing how to
configure the corresponding :class:`~logging.Formatter` instance. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
bb0019ca-c5b7-408b-a705-c67b25a506eb | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,042 | supabase-export-v2 | 4d26d7b4691db1d5 | and ``filters`` entries, and process only the ``level`` settings in the ``handlers`` entries, and the ``level`` and ``propagate`` settings in the ``loggers`` and ``root`` entries.
Using a value in the configuration dict lets configurations to be sent
over the wire as pickled dicts to a socket listener. Thus, the loggin... | trusted_official_docs | CPython Docs | and ``filters`` entries, and process only the ``level`` settings in the ``handlers`` entries, and the ``level`` and ``propagate`` settings in the ``loggers`` and ``root`` entries.
Using a value in the configuration dict lets configurations to be sent
over the wire as pickled dicts to a socket listener. Thus, the loggin... | and ``filters`` entries, and process only the ``level`` settings in the ``handlers`` entries, and the ``level`` and ``propagate`` settings in the ``loggers`` and ``root`` entries.
Using a value in the configuration dict lets configurations to be sent
over the wire as pickled dicts to a socket listener. Thus, the loggin... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
c005db4b-7e0c-48b1-90a7-be00826a8700 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,039 | supabase-export-v2 | 571d4ce8bfd06743 | Incremental Configuration """""""""""""""""""""""""
It is difficult to provide complete flexibility for incremental
configuration. For example, because objects such as filters
and formatters are anonymous, once a configuration is set up, it is
not possible to refer to such anonymous objects when augmenting a
configurat... | trusted_official_docs | CPython Docs | Incremental Configuration """""""""""""""""""""""""
It is difficult to provide complete flexibility for incremental
configuration. For example, because objects such as filters
and formatters are anonymous, once a configuration is set up, it is
not possible to refer to such anonymous objects when augmenting a
configurat... | Incremental Configuration """""""""""""""""""""""""
It is difficult to provide complete flexibility for incremental
configuration. For example, because objects such as filters
and formatters are anonymous, once a configuration is set up, it is
not possible to refer to such anonymous objects when augmenting a
configurat... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
c186b3ce-836b-4163-ab6d-45a9068001bc | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,120 | supabase-export-v2 | 8308e03f0687113c | Configuration file format ^^^^^^^^^^^^^^^^^^^^^^^^^
The configuration file format understood by :func:`fileConfig` is based on
:mod:`configparser` functionality. The file must contain sections called
``[loggers]``, ``[handlers]`` and ``[formatters]`` which identify by name the
entities of each type which are defined in... | trusted_official_docs | CPython Docs | Configuration file format ^^^^^^^^^^^^^^^^^^^^^^^^^
The configuration file format understood by :func:`fileConfig` is based on
:mod:`configparser` functionality. The file must contain sections called
``[loggers]``, ``[handlers]`` and ``[formatters]`` which identify by name the
entities of each type which are defined in... | Configuration file format ^^^^^^^^^^^^^^^^^^^^^^^^^
The configuration file format understood by :func:`fileConfig` is based on
:mod:`configparser` functionality. The file must contain sections called
``[loggers]``, ``[handlers]`` and ``[formatters]`` which identify by name the
entities of each type which are defined in... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
c30c39a3-fdf3-47b8-8f15-955e05466ff3 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,131 | supabase-export-v2 | d21ce580c74d22a6 | [logger_root] level=NOTSET handlers=hand01
The ``level`` entry can be one of ``DEBUG, INFO, WARNING, ERROR, CRITICAL`` or
``NOTSET``. For the root logger only, ``NOTSET`` means that all messages will be
logged. Level values are :ref:`evaluated <func-eval>` in the context of the ``logging``
package's namespace. | trusted_official_docs | CPython Docs | [logger_root] level=NOTSET handlers=hand01
The ``level`` entry can be one of ``DEBUG, INFO, WARNING, ERROR, CRITICAL`` or
``NOTSET``. For the root logger only, ``NOTSET`` means that all messages will be
logged. Level values are :ref:`evaluated <func-eval>` in the context of the ``logging``
package's namespace. | [logger_root] level=NOTSET handlers=hand01
The ``level`` entry can be one of ``DEBUG, INFO, WARNING, ERROR, CRITICAL`` or
``NOTSET``. For the root logger only, ``NOTSET`` means that all messages will be
logged. Level values are :ref:`evaluated <func-eval>` in the context of the ``logging``
package's namespace. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
c3aa326f-b3c2-40fd-b795-8184f67b2c83 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,106 | supabase-export-v2 | a5e0048ff1c9242b | and :meth:`Queue.get <queue.Queue.get>` public API. For instance, this may be an actual instance of :class:`queue.Queue` or a subclass thereof, or a proxy obtained by :meth:`multiprocessing.managers.SyncManager.Queue`.
This is of course only possible if you are constructing or modifying
the configuration dictionary in... | trusted_official_docs | CPython Docs | and :meth:`Queue.get <queue.Queue.get>` public API. For instance, this may be an actual instance of :class:`queue.Queue` or a subclass thereof, or a proxy obtained by :meth:`multiprocessing.managers.SyncManager.Queue`.
This is of course only possible if you are constructing or modifying
the configuration dictionary in... | and :meth:`Queue.get <queue.Queue.get>` public API. For instance, this may be an actual instance of :class:`queue.Queue` or a subclass thereof, or a proxy obtained by :meth:`multiprocessing.managers.SyncManager.Queue`.
This is of course only possible if you are constructing or modifying
the configuration dictionary in... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
c6fa551b-0978-4fa2-b264-88f82f4c10ec | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,049 | supabase-export-v2 | fa7b0765d7bda0c1 | is another id # configuration of handler with id 'h2' goes here formatter: precise loggers: foo.bar.baz: # other configuration for logger 'foo.bar.baz' handlers: [h1, h2]
(Note: YAML used here because it's a little more readable than the
equivalent Python source form for the dictionary.) | trusted_official_docs | CPython Docs | is another id # configuration of handler with id 'h2' goes here formatter: precise loggers: foo.bar.baz: # other configuration for logger 'foo.bar.baz' handlers: [h1, h2]
(Note: YAML used here because it's a little more readable than the
equivalent Python source form for the dictionary.) | is another id # configuration of handler with id 'h2' goes here formatter: precise loggers: foo.bar.baz: # other configuration for logger 'foo.bar.baz' handlers: [h1, h2]
(Note: YAML used here because it's a little more readable than the
equivalent Python source form for the dictionary.) | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
d2e21c08-c59b-40f3-be76-5923e587ff5f | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,123 | supabase-export-v2 | 1ea23a92259e912a | future enhancements to configuration functionality will be added to :func:`dictConfig`, so it's worth considering transitioning to this newer API when it's convenient to do so.
Examples of these sections in the file are given below. | trusted_official_docs | CPython Docs | future enhancements to configuration functionality will be added to :func:`dictConfig`, so it's worth considering transitioning to this newer API when it's convenient to do so.
Examples of these sections in the file are given below. | future enhancements to configuration functionality will be added to :func:`dictConfig`, so it's worth considering transitioning to this newer API when it's convenient to do so.
Examples of these sections in the file are given below. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
d3b57d7b-d8b0-4a66-a7f8-77a5e1d3f120 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,136 | supabase-export-v2 | d8c28154c6b9adee | [logger_parser] level=DEBUG handlers=hand01 propagate=1 qualname=compiler.parser
The ``level`` and ``handlers`` entries are interpreted as for the root logger,
except that if a non-root logger's level is specified as ``NOTSET``, the system
consults loggers higher up the hierarchy to determine the effective level of the... | trusted_official_docs | CPython Docs | [logger_parser] level=DEBUG handlers=hand01 propagate=1 qualname=compiler.parser
The ``level`` and ``handlers`` entries are interpreted as for the root logger,
except that if a non-root logger's level is specified as ``NOTSET``, the system
consults loggers higher up the hierarchy to determine the effective level of the... | [logger_parser] level=DEBUG handlers=hand01 propagate=1 qualname=compiler.parser
The ``level`` and ``handlers`` entries are interpreted as for the root logger,
except that if a non-root logger's level is specified as ``NOTSET``, the system
consults loggers higher up the hierarchy to determine the effective level of the... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
d3d92b72-6ca0-490a-931d-1214cac687ec | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,040 | supabase-export-v2 | 185da09d8ff5abb2 | filters and formatters are anonymous, once a configuration is set up, it is not possible to refer to such anonymous objects when augmenting a configuration.
Furthermore, there is not a compelling case for arbitrarily altering
the object graph of loggers, handlers, filters, formatters at
run-time, once a configuration i... | trusted_official_docs | CPython Docs | filters and formatters are anonymous, once a configuration is set up, it is not possible to refer to such anonymous objects when augmenting a configuration.
Furthermore, there is not a compelling case for arbitrarily altering
the object graph of loggers, handlers, filters, formatters at
run-time, once a configuration i... | filters and formatters are anonymous, once a configuration is set up, it is not possible to refer to such anonymous objects when augmenting a configuration.
Furthermore, there is not a compelling case for arbitrarily altering
the object graph of loggers, handlers, filters, formatters at
run-time, once a configuration i... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
d775979d-7efb-4fd0-b513-7a46a53a2621 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,107 | supabase-export-v2 | 029204ba186231a1 | This is of course only possible if you are constructing or modifying the configuration dictionary in code.
* A string that resolves to a callable which, when called with no arguments, returns
the queue instance to use. That callable could be a :class:`queue.Queue` subclass
or a function which returns a suitable queue... | trusted_official_docs | CPython Docs | This is of course only possible if you are constructing or modifying the configuration dictionary in code.
* A string that resolves to a callable which, when called with no arguments, returns
the queue instance to use. That callable could be a :class:`queue.Queue` subclass
or a function which returns a suitable queue... | This is of course only possible if you are constructing or modifying the configuration dictionary in code.
* A string that resolves to a callable which, when called with no arguments, returns
the queue instance to use. That callable could be a :class:`queue.Queue` subclass
or a function which returns a suitable queue... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
d80f744f-084e-459d-b7df-5c04cf547ab9 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,074 | supabase-export-v2 | fb4f57095134e5d4 | Handler configuration order """""""""""""""""""""""""""
Handlers are configured in alphabetical order of their keys, and a configured
handler replaces the configuration dictionary in (a working copy of) the
``handlers`` dictionary in the schema. If you use a construct such as
``cfg://handlers.foo``, then initially ``ha... | trusted_official_docs | CPython Docs | Handler configuration order """""""""""""""""""""""""""
Handlers are configured in alphabetical order of their keys, and a configured
handler replaces the configuration dictionary in (a working copy of) the
``handlers`` dictionary in the schema. If you use a construct such as
``cfg://handlers.foo``, then initially ``ha... | Handler configuration order """""""""""""""""""""""""""
Handlers are configured in alphabetical order of their keys, and a configured
handler replaces the configuration dictionary in (a working copy of) the
``handlers`` dictionary in the schema. If you use a construct such as
``cfg://handlers.foo``, then initially ``ha... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
d826504b-a269-425a-989e-827dadb30590 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,002 | supabase-export-v2 | 77d17fac1039d757 | Configuration dictionary schema ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Describing a logging configuration requires listing the various
objects to create and the connections between them; for example, you
may create a handler named 'console' and then say that the logger
named 'startup' will send its messages to the 'console' h... | trusted_official_docs | CPython Docs | Configuration dictionary schema ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Describing a logging configuration requires listing the various
objects to create and the connections between them; for example, you
may create a handler named 'console' and then say that the logger
named 'startup' will send its messages to the 'console' h... | Configuration dictionary schema ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Describing a logging configuration requires listing the various
objects to create and the connections between them; for example, you
may create a handler named 'console' and then say that the logger
named 'startup' will send its messages to the 'console' h... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
d90e1e07-1d78-44db-9e6c-7c19353fa961 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,982 | supabase-export-v2 | 034842bd50137321 | :param encoding: The encoding used to open file when *fname* is filename.
.. versionchanged:: 3.4
An instance of a subclass of :class:`~configparser.RawConfigParser` is
now accepted as a value for ``fname``. This facilitates: | trusted_official_docs | CPython Docs | :param encoding: The encoding used to open file when *fname* is filename.
.. versionchanged:: 3.4
An instance of a subclass of :class:`~configparser.RawConfigParser` is
now accepted as a value for ``fname``. This facilitates: | :param encoding: The encoding used to open file when *fname* is filename.
.. versionchanged:: 3.4
An instance of a subclass of :class:`~configparser.RawConfigParser` is
now accepted as a value for ``fname``. This facilitates: | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
defa22fd-230c-41e7-9ec0-7c72468497ae | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 29,977 | supabase-export-v2 | f10b4ab03a2582c8 | allowing an end user to select from various pre-canned configurations (if the developer provides a mechanism to present the choices and load the chosen configuration).
It will raise :exc:`FileNotFoundError` if the file
doesn't exist and :exc:`RuntimeError` if the file is invalid or
empty. | trusted_official_docs | CPython Docs | allowing an end user to select from various pre-canned configurations (if the developer provides a mechanism to present the choices and load the chosen configuration).
It will raise :exc:`FileNotFoundError` if the file
doesn't exist and :exc:`RuntimeError` if the file is invalid or
empty. | allowing an end user to select from various pre-canned configurations (if the developer provides a mechanism to present the choices and load the chosen configuration).
It will raise :exc:`FileNotFoundError` if the file
doesn't exist and :exc:`RuntimeError` if the file is invalid or
empty. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
df2f82f9-00c7-44c1-81cf-ab7e0f50567c | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,063 | supabase-export-v2 | e5fcdea9fb5fc892 | { '()' : 'my.package.customFormatterFactory', 'bar' : 'baz', 'spam' : 99.9, 'answer' : 42 }
and this contains the special key ``'()'``, which means that
user-defined instantiation is wanted. In this case, the specified
factory callable will be used. If it is an actual callable it will be
used directly - otherwise, if y... | trusted_official_docs | CPython Docs | { '()' : 'my.package.customFormatterFactory', 'bar' : 'baz', 'spam' : 99.9, 'answer' : 42 }
and this contains the special key ``'()'``, which means that
user-defined instantiation is wanted. In this case, the specified
factory callable will be used. If it is an actual callable it will be
used directly - otherwise, if y... | { '()' : 'my.package.customFormatterFactory', 'bar' : 'baz', 'spam' : 99.9, 'answer' : 42 }
and this contains the special key ``'()'``, which means that
user-defined instantiation is wanted. In this case, the specified
factory callable will be used. If it is an actual callable it will be
used directly - otherwise, if y... | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
e2720201-677a-4af7-93a8-c437fa1c7408 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,067 | supabase-export-v2 | 831e0966c174c369 | with the names of the keyword arguments used in the call. The ``'()'`` also serves as a mnemonic that the corresponding value is a callable.
.. versionchanged:: 3.11
The ``filters`` member of ``handlers`` and ``loggers`` can take
filter instances in addition to ids. | trusted_official_docs | CPython Docs | with the names of the keyword arguments used in the call. The ``'()'`` also serves as a mnemonic that the corresponding value is a callable.
.. versionchanged:: 3.11
The ``filters`` member of ``handlers`` and ``loggers`` can take
filter instances in addition to ids. | with the names of the keyword arguments used in the call. The ``'()'`` also serves as a mnemonic that the corresponding value is a callable.
.. versionchanged:: 3.11
The ``filters`` member of ``handlers`` and ``loggers`` can take
filter instances in addition to ids. | python, official-docs, cpython, P0 | Local_Trusted_Corpus | |
e37cd267-bbc1-412c-a40a-2996b53a2d75 | CPython Docs | file://datasets/cpython/Doc/library/logging.config.rst | unknown | e800cdf0-5c99-47e3-b083-38de35bdaf73 | 30,133 | supabase-export-v2 | fd5521ec9bd6c753 | handler names, which must appear in the ``[handlers]`` section. These names must appear in the ``[handlers]`` section and have corresponding sections in the configuration file.
For loggers other than the root logger, some additional information is required. This is illustrated by the following example. | trusted_official_docs | CPython Docs | handler names, which must appear in the ``[handlers]`` section. These names must appear in the ``[handlers]`` section and have corresponding sections in the configuration file.
For loggers other than the root logger, some additional information is required. This is illustrated by the following example. | handler names, which must appear in the ``[handlers]`` section. These names must appear in the ``[handlers]`` section and have corresponding sections in the configuration file.
For loggers other than the root logger, some additional information is required. This is illustrated by the following example. | python, official-docs, cpython, P0 | Local_Trusted_Corpus |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.