[vmchecker-dev] logger naming

[Alexandru Moșoi]

2009/4/28 Lucian Adrian Grijincu <lucian.grijincu at gmail.com>:
> Alexandru wanted us to kill "vmchecker.", because it is implied.
> Well, not exactly:

>  DEBUG:paramiko.transport:Switch to new keys ...
>  INFO:vmchecker.callback:Remote server host key is valid.
>  DEBUG:paramiko.transport:userauth is OK
As a separate issue, I don't see why we need other modules. When
configuring the logging module using a file (ie. using
logging.config.fileConfig) I'll need to white-list which modules to
enable logging for. We're not going to white-list all paramiko &
paramiko submodules. Check Vinay Sajip's (author of logging module) to
my post on comp.lang.python [0]

> This is how output looks right now. I'd argue that having "vmchecker."
> in front of names is better: we see exactly which message was created
> by us and what was created by other components.
> This will be more useful when we'll bring in python-libvirt and other
> python modules.
most modules do not have logging (not even stdlib).

Nevertheless, I'm in favour of reverting to
_logger.getLogger('vmchecker.submodule') and since I made the silent
change I'll take care of it [1].

[0] http://groups.google.com/group/comp.lang.python/msg/434e7e828331ac90
[1] http://github.com/vmchecker/vmchecker/issues/#issue/9

-- 
Alexandru Moșoi
http://alexandru.mosoi.googlepages.com

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html