python-checkins at python
Nov 24, 2009, 12:20 AM
Post #1 of 1
(135 views)
Permalink
|
|
r76475 - peps/trunk/pep-0391.txt
|
|
Author: vinay.sajip
Date: Tue Nov 24 07:52:39 2009
New Revision: 76475
Log:
Minor changes, additions and clarifications.
Modified:
peps/trunk/pep-0391.txt
Modified: peps/trunk/pep-0391.txt
==============================================================================
--- peps/trunk/pep-0391.txt (original)
+++ peps/trunk/pep-0391.txt Tue Nov 24 07:52:39 2009
@@ -305,9 +305,9 @@
custom:
(): my.package.MyHandler
- alternate: int://handlers.file
+ alternate: cfg://handlers.file
-The literal string ``'int://handlers.file'`` will be resolved in an
+The literal string ``'cfg://handlers.file'`` will be resolved in an
analogous way to the strings with the ``ext://`` prefix, but looking
in the configuration itself rather than the import namespace. The
mechanism will allow access by dot or by index, in a similar way to
@@ -323,29 +323,29 @@
- dev_team [at] domain
subject: Houston, we have a problem.
-in the configuration, the string ``'int://handlers'`` would resolve to
-the dict with key ``handlers``, the string ``'int://handlers.email``
+in the configuration, the string ``'cfg://handlers'`` would resolve to
+the dict with key ``handlers``, the string ``'cfg://handlers.email``
would resolve to the dict with key ``email`` in the ``handlers`` dict,
-and so on. The string ``'int://handlers.email.toaddrs[1]`` would
+and so on. The string ``'cfg://handlers.email.toaddrs[1]`` would
resolve to ``'dev_team.domain.tld'`` and the string
-``'int://handlers.email.toaddrs[0]'`` would resolve to the value
+``'cfg://handlers.email.toaddrs[0]'`` would resolve to the value
``'support_team [at] domain'``. The ``subject`` value could be accessed
-using either ``'int://handlers.email.subject'`` or, equivalently,
-``'int://handlers.email[subject]'``. The latter form only needs to be
+using either ``'cfg://handlers.email.subject'`` or, equivalently,
+``'cfg://handlers.email[subject]'``. The latter form only needs to be
used if the key contains spaces or non-alphanumeric characters. If 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 ``int://handlers.myhandler.mykey.123``, this will
+Given a string ``cfg://handlers.myhandler.mykey.123``, this will
resolve to ``config_dict['handlers']['myhandler']['mykey']['123']``.
-If the string is specified as ``int://handlers.myhandler.mykey[123]``,
+If the string is specified as ``cfg://handlers.myhandler.mykey[123]``,
the system will attempt to retrieve the value from
-``config_dict['handlers']['myhandler']['mykey'][123]``, ad fall back
+``config_dict['handlers']['myhandler']['mykey'][123]``, and fall back
to ``config_dict['handlers']['myhandler']['mykey']['123']`` if that
fails.
-Note: the ``ext`` and ``int`` prefixes are provisional. If better
+Note: the ``ext`` and ``cfg`` prefixes are provisional. If better
alternatives are suggested during the PEP review process, they will be
used.
@@ -484,7 +484,11 @@
If the specified value is ``True``, the configuration is processed
as described in the section on `Incremental Configuration`_, below.
-
+* `disable_existing_loggers` - whether any existing loggers are to be
+ disabled. This setting mirrors the parameter of the same name in
+ ``fileConfig()``. If absent, this parameter defaults to ``True``.
+ This value is ignored if `incremental` is ``True``.
+
A Working Example
-----------------
@@ -567,7 +571,7 @@
It's certainly possible to provide incremental configuration by other
means, for example making ``dictConfig()`` take an ``incremental``
keyword argument which defaults to ``False``. The reason for
-suggesting that a flag in the configuration dict be used is that it
+suggesting that a value in the configuration dict be used is that it
allows for configurations to be sent over the wire as pickled dicts
to a socket listener. Thus, the logging verbosity of a long-running
application can be altered over time with no need to stop and
_______________________________________________
Python-checkins mailing list
Python-checkins [at] python
http://mail.python.org/mailman/listinfo/python-checkins
|
