|
Size: 590
Comment: slowness
|
Size: 1023
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| An alternate configuration mechanism is provided by the [[http://www.zope.org/Members/fdrake/zconfig/|ZConfig]] package ([[http://pypi.python.org/pypi/ZConfig/|PyPI]]). | An alternate configuration mechanism is provided by the [[http://www.zope.org/Members/fdrake/zconfig/|ZConfig]] package ([[http://pypi.python.org/pypi/ZConfig/|PyPI]]). (Note ZConfig is not a small package to pull in.) |
| Line 15: | Line 15: |
| * API uses camelCase (ie is not PEP8 compatible) | * API uses camelCase (goes against PEP8 recommendation and most of the stdlib) |
| Line 18: | Line 18: |
* Doesn't have runtime scoping (i.e., log messages handled based on the call stack) * Difficult to extend log records * Difficult to add general context to log messages (e.g., add the request URL to all logging messages during the request) * By default it does nothing; basicConfig makes it do something but makes it hard to tweak logging. |
This page should cover pros and cons of current stdlib logging package.
Pros
* Almost every feature you could want from logging package is there
Cons
* Docs are not complete
* Config files are a little bit hard to comprehend
An alternate configuration mechanism is provided by the ZConfig package (PyPI). (Note ZConfig is not a small package to pull in.)
* API uses camelCase (goes against PEP8 recommendation and most of the stdlib)
* Rather slow considering the large number of function calls performed internally to check which handler to use
* Doesn't have runtime scoping (i.e., log messages handled based on the call stack)
* Difficult to extend log records
* Difficult to add general context to log messages (e.g., add the request URL to all logging messages during the request)
* By default it does nothing; basicConfig makes it do something but makes it hard to tweak logging.