Re: [pyusb-users] pyusb logging and errors behavior

2011-08-30 Thread Wander Lairson Costa
2011/8/30 chris clark : > On Mon, Aug 29, 2011 at 6:16 AM, Wander Lairson Costa > wrote: >> I created a patch to this problem, please test it and report >> the status, so I can commit it to the source tree. Thanks for the bug >> report. > > > Wander, > > the patch worked and behaved as expected! C

Re: [pyusb-users] pyusb logging and errors behavior

2011-08-30 Thread Wander Lairson Costa
2011/8/30 chris clark : > On Mon, Aug 29, 2011 at 6:16 AM, Wander Lairson Costa > wrote: >> I created a patch to this problem, please test it and report >> the status, so I can commit it to the source tree. Thanks for the bug >> report. > > > Wander, > > the patch worked and behaved as expected! C

Re: [pyusb-users] pyusb logging and errors behavior

2011-08-30 Thread Wander Lairson Costa
2011/8/29 Karl P : > > 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

Re: [pyusb-users] pyusb logging and errors behavior

2011-08-29 Thread chris clark
On Mon, Aug 29, 2011 at 6:16 AM, Wander Lairson Costa wrote: > I created a patch to this problem, please test it and report > the status, so I can commit it to the source tree. Thanks for the bug > report. Wander, the patch worked and behaved as expected! Critical/Fatals can still show up, whic

Re: [pyusb-users] pyusb logging and errors behavior

2011-08-29 Thread Karl P
>> >> I personally consider what Chris reports to be "expected behaviour" > > We may be getting into personal preference here. I would NOT expect to > see a library's debug output when running my script (or application). > If that behavior/behaviour were to be common, one would end up seeing > d

Re: [pyusb-users] pyusb logging and errors behavior

2011-08-29 Thread chris clark
Wander - thanks for the patch and quick response. I'll test that out. Karl. see below. On Mon, Aug 29, 2011 at 1:47 PM, Karl P wrote: > 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 > l

Re: [pyusb-users] pyusb logging and errors behavior

2011-08-29 Thread Karl P
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.getLog

Re: [pyusb-users] pyusb logging and errors behavior

2011-08-29 Thread Wander Lairson Costa
2011/8/27 chris clark : > I know pyusb (in svn) is currently not really supported/ready but I have a > usability question/observation. > Although not ready, many people are using it without problems. And I am pleasure to support any question in the mailing list. > If I have a (dumb) example script

[pyusb-users] pyusb logging and errors behavior

2011-08-27 Thread chris clark
I know pyusb (in svn) is currently not really supported/ready but I have a usability question/observation. If I have a (dumb) example script that uses the "basic" logging settings and pyusb fails to load a backend the OpenUSB load attempt ends up being logged when it too fails, a traceback is also