From: Wander L. C. <wan...@gm...> - 2012-03-29 11:48:10
|
2012/3/29 Tormod Volden <lis...@gm...>: > On Thu, Mar 29, 2012 at 12:32 PM, Wander Lairson Costa wrote: >> Yes, this is a known problem that was already reported before. PyUSB >> 0.4 was very flexible in managing the buffer types, and PyUSB 1.0 is >> not that so. I could not find yet a simple and elegant solution for >> this problem, but try to mimic to behavior of the C version of PyUSB. > > Thanks. I could not find it in the bug tracker, but I found a post > from Sarah Messer seeing the same problem here: > http://sourceforge.net/mailarchive/message.php?msg_id=27131804 > There it is. > Maybe we should just try return array.array('c', data) before or after > trying array.array('u', data)? > This maybe a workaround for this specific case, but I mimic the behavior of the C version, things get more complicated. Anyway, if you provide a patch, I will accept, it is better than nothing. > BTW, how is the use of unicode strings meant to work? Each string > character LSB is sent to the device? > I don't remember for sure right now, but I think all bytes are sent as a linear buffer... -- Best Regards, Wander Lairson Costa |