Hi,
recently I had a use case where I wanted to use logging in two
completely separate parts of the same process. One of them
needs to create instances a specific Logger subclass, while the
other is fine with the default loggers.
I got around the problem of the unique root node by using two
Mana
Georg Brandl gmx.net> writes:
> Making the loggerClass configurable per manager would solve the
> problem for me, and AFAICS since most applications don't use
> different managers anyway, there should not be any detrimental
> effects. What do you think?
Seems reasonable. Apart from the API to s
Full View
PEP 391 is, I believe, ready for review.
http://www.python.org/dev/peps/pep-0391/
I've
also worked up an implementation, though not yet checked it in: it's
available as a module "dictconfig.py" with accompanying unit tests in
"test_dictconfig.py", at:
http://bitbucket.org/vinay.sajip/d
I would recommend removing the class keyword and replacing it with the
() as you have in the custom examples or replacing () with class so it
is uniform across all config options
handlers:
file:
class : logging.handlers.RotatingFileHandler
formatter: precise
filename: logconfig.log
ma
Vinay Sajip wrote:
Full View
PEP 391 is, I believe, ready for review.
http://www.python.org/dev/peps/pep-0391/
This is my first reading of this. Comments:
nit: I believe "both of these serialization formats allow
deserialization of Python dictionaries." should be "... to Python
dictionaries
Hi all,
I got an MSI build working on my WinXP VM just now, and I wanted to
touch base with whomever it is that is maintaining this (wonderful!)
set of scripts...
I ran into three problems, and I managed to figure out two of them; the third
wasn't fatal. Note, the diff of my fixed checkout is at
