Size: 1079
Comment:
|
Size: 1071
Comment: fix formatting
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
* Almost every feature you could want from logging package is there | * Almost every feature you could want from logging package is there |
Line 9: | Line 9: |
* Docs are not complete * Config files are a little bit hard to comprehend |
* Docs are not complete * Config files are a little bit hard to comprehend |
Line 14: | Line 12: |
* 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. * filters are an abstract class instead of callables |
* 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. * filters are an abstract class instead of callables |
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
- 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.
- filters are an abstract class instead of callables