At 09:04 PM 6/5/2006 -0400, Jim Jewett wrote: >On 6/4/06, Phillip J. Eby <pje at telecommunity.com> wrote: > > can we please delay the import until it's actually needed? i.e., > > until after some logging option is enabled? > >I have asked her to make this change. > >I don't like the extra conditional dance it causes, but I agree that >not wanting to log is a valid use case. > >On the other hand, the one-time import cost is pretty low for a >long-running process, and eventually gets paid if any other module >calls logging. Would it make more sense to offer a null package that >can be installed earlier in the search path if you want to truly >disable logging? I notice you've completely avoided the question of whether this should be being done at all. It sounds like Fredrik is -1 on this even for the modules that I'm not -1 on. As far as I can tell, this PEP hasn't actually been discussed. Please don't waste time changing modules for which there is no consensus that this *should* be done. The original discussion that occurred prior to PEP 337's creation discussed only modules that *already* do some kind of logging. There was no discussion of changing *all* debugging output to use the logging module, nor of adding logging to modules that do not even have any debugging output (e.g. pkgutil).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4