On Mar 29, 2012, at 7:30 PM, Tormod Volden <lists.tor...@gmail.com> wrote:
> 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
>
> Maybe we should just try return array.array('c', data) before or after
> trying array.array('u', data)?
>
> BTW, how is the use of unicode strings meant to work? Each string
> character LSB is sent to the device?
>
My recommendation is that UTF16 and UTF32 be an exception unless a byte order
is specified or BOM is present.
Other option is to default to little endian, as USB is intel driven. Then let
it be overridden to big endian.
Steve
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
pyusb-users mailing list
pyusb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pyusb-users
