The method was not prepared for Python at all, and that length argument was not deduced from the object passed.
M.
Date: Mon, 26 Oct 2015 16:45:52 -0700
From: cbrackert@xxxx
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
CC: xantares09@xxxxxxxxxxx
Subject: Re: Re: ftdi.write_data doesn’t work with some python3 unicode strings
The patch is working great. Thanks guys! The dumb workaround that I was using meant calling the library with python 3 unicode strings, but once I updated those to bytes everything worked.
The code I’m working with used to call ftdi.write_data with a third parameter for “length” but now that is not allowed. Was that unnecesarry to begin with?
On Fri, Oct 23, 2015 at 5:16 PM, Chris Brackert
<cbrackert@xxxx> wrote:
I need to get my test hardware setup again. I should be able to get to this early next week and then I will report back. Thanks!
On Fri, Oct 23, 2015 at 4:22 AM, Thomas Jarosch
<thomas.jarosch@xxxxxxxxxxxxx> wrote:
Hi Chris,
On Friday, 16. October 2015 13:40:41 Thomas Jarosch wrote:
> > I know this fix is not the proper way to do this but it is working for
> > me. Can you please investigate this issue and fix the library to work
> > with all python3 strings?
please test the fix Michel provided and let me know if it works for you.
Thanks,
Thomas
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
libftdi - see
http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to
libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx