[Python-Dev] Stdlib Logging questions (PEP 337 SoC)
Fredrik Lundh
fredrik at pythonware.com
Mon Jun 5 09:42:42 CEST 2006
More information about the Python-Dev mailing list
Mon Jun 5 09:42:42 CEST 2006
- Previous message: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)
- Next message: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Phillip J. Eby wrote: > If this *has* to be added to the modules that don't currently do any > logging, can we please delay the import until it's actually needed? now that we've had a needforspeed sprint, it's clear that it's time to start working on slowing things down again ;-) > I think it would be a good idea to revisit the module list. I can see a > reasonable case for the BaseHTTP stuff and asyncore needing a logging > framework, if you plan to make them part of some larger framework -- the > configurability would be a plus asyncore's logging is configurable through subclassing, as is everything else in asyncore (the components don't do anything if you don't subclass them). mapping to the logger module by default will save 5-10 lines of code in an application that wants to use the logger module. *replacing* the existing logging hooks with the logger module will break tons of stuff. BaseHTTP only does webserver-style logging, as far as I can tell. </F>
- Previous message: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)
- Next message: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list