2013/10/29 Johannes Stezenbach <j...@sig21.net>: > Hi, > Hi Johannes,
> On Wed, Oct 16, 2013 at 08:51:24AM -0300, Wander Lairson Costa wrote: >> I am proud to announce that PyUSB 1.0.0 beta is out. > ... >> TODO >> ---- >> >> * More tests with legacy module. >> * Isochronous transfers for libusb-win32. >> >> Download page >> ------------- >> >> https://sourceforge.net/projects/pyusb/files/PyUSB%201.0/1.0.0-beta-1/ >> >> This release took much more time than I was expecting to, so I would like >> to thank you all for your patience, and specially for those whose contributed >> for this release. > > I've been using pyusb-1.0.0-a1.tar.gz some time back, and > the new beta release still works perfectly on Linux for > some ad-hoc testing. > > One remark: The "Let's get it started" example in > docs/tutorial.rst looks confusing, why does it do this: > > cfg = dev.get_active_configuration() > interface_number = cfg[(0,0)].bInterfaceNumber > alternate_setting = usb.control.get_interface(dev, interface_number) > intf = usb.util.find_descriptor( > cfg, bInterfaceNumber = interface_number, > bAlternateSetting = alternate_setting > ) > > instead of just this:? > > intf = cfg[(0,0)] > The code above finds the interface by its interface number, not its index inside the configuration (they are not necessarily the same thing). > Also, the code lacks an > > intf.set_altsetting() > set_altsetting is only needed by device with alternate settings. > otherwise the EPs are not reset which might lead to errors > (e.g. STALL is not cleaared from previous use), and Linux complains: > Stalled endpoints are not something expected in normal cases. > [2249737.372143] usb 1-1.1: usbfs: process 32478 (python) did not claim > interface 0 before use > Interface claiming, in another hand, is handled internally by PyUSB, this might be a bug. > > I hope you can do the 1.0.0 final release soon and PyUSB 1.x will be picked > up by Linux distributions. Currently most seem to ship PyUSB 0.4, which > is a pity given the 1.0 API is so much better. It slso would be a good idea > to clearly state in the README that both Python 2.x and Python 3.x are > supported. > I hope too. -- Best Regards, Wander Lairson Costa ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel