On Tue, Apr 6, 2010 at 9:26 PM, Wander Lairson <wander.lair...@gmail.com> wrote:
> I added some preliminary log support to PyUSB at revision 56, it uses
> the logging module. Currently, you can define the environment variable
> PYUSB_DEBUG_LEVEL with the following values: critical, error, warning,
> information, debug. Running tests with debug defined, explain why
> get_backend failed with a stack trace. I hope this can help to find
> bugs. It is very raw and there are few messages yet.
>
Hmm, the error is rather strange.
C:\cygwin\home\mcuee\mcu\pyusb\pyusb\tests>c:\Python26\python.exe
Python 2.6.5 (r265:79096, Mar 19 2010, 21:48:26) [MSC v.1500 32 bit (Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import usb.core
>>> import usb.backend.libusb10
>>> a=usb.backend.libusb10.get_backend()
2010-04-06 21:58:36,944 DEBUG:usb.backend.libusb10:Error loading libusb 1.0 back
end
Traceback (most recent call last):
File "c:\Python26\lib\site-packages\usb\backend\libusb10.py", line 558, in get
_backend
_init = _Initializer()
File "c:\Python26\lib\site-packages\usb\backend\libusb10.py", line 375, in __i
nit__
_check(_lib.libusb_init(None))
ValueError: Procedure probably called with too many arguments (4 bytes in excess
)
Exception ValueError: 'Procedure probably called with too many arguments (4 byte
s in excess)' in <bound method _Initializer.__del__ of <usb.backend.libusb10._In
itializer object at 0x026A6910>> ignored
--
Xiaofan http://mcuee.blogspot.com
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
pyusb-users mailing list
pyusb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pyusb-users
