2011/8/29 Karl P <ka...@tweak.net.au>:
>
> Forgive me if I'm wrong, and I haven't actually tested this out, but doesn't
> the
> new behaviour mean that if I am using python logging, and I set the logging
> level on my application root logger to INFO (for instance) that I no longer
> see
> logging from pyusb without an explicit...
>
> logging.getLogger("usb").setLevel(logging.INFO) ?
>
> Isn't this the exact _opposite_ of what libraries are meant to do for logging?
>
> If you are using logging in your app, and you don't want to get logging from a
> library that you are using, I expect the user to turn off logging for that
> library. At least, that's what _I_ expect. (it's what log4j/slf4j does, and
> it's also how all of my apps and libraries work.
>
> I personally consider what Chris reports to be "expected behaviour"
>
I understand your point of view, but for the objective of logging in
PyUSB, which is to enable log only to debug problems with the library
itself, what Chris reported is truly a bug. The fact that PyUSB uses
the logging module is just an implementation detail, and it should not
be influenced by app configuration if the user doesn't wrote code to
do so. Of course PyUSB is directed to the user, and if most users
prefer the original behavior, I can change things back, but it is not
the original proposal of log in PyUSB.
--
Best Regards,
Wander Lairson Costa
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
pyusb-users mailing list
pyusb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pyusb-users
