[Python-Dev] Consistent logging in the standard library (original) (raw)
Matthew F. Barnes mfb at lotusland.dyndns.org
Wed Sep 17 20:22:27 EDT 2003
- Previous message: [Python-Dev] Consistent logging in the standard library
- Next message: [Python-Dev] Consistent logging in the standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Skip Montanaro said:
Barry> So the idea would be to be able to write "import .logging" and Barry> definitely get the global logging package. Using underscore in Barry> the logger would mirror this mnemonic for globalness. The connection seems tenuous, at best. If I log messages to syslog and and that file is later viewed or summarized by a third party, "python" seems a lot more useful than "" or even "stdlib".
I agree with Barry that a name should be given to the standard library "package" and that the namespace reserved in the logging hierarchy for standard library modules should match this name.
On the other hand, "_" is making me have unpleasant Perl flashbacks. shiver So I also agree with Skip that something more verbose would be more useful.
I'm okay with waiting to see what becomes of Barry's idea before deciding on a logging namespace.
Barry:
Not to get too far off-topic, but I'm curious what this statement would do:
from _ import *
And was this notation ever considered?
import .logging
(Not that that would help us much with the logging namespace issue. :-)
Matthew Barnes
- Previous message: [Python-Dev] Consistent logging in the standard library
- Next message: [Python-Dev] Consistent logging in the standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]