Skip to content

Conversation

@bhass1
Copy link

@bhass1 bhass1 commented Apr 26, 2024

Fixes Issue #359

I considered converting it to a self.log.warning(), but the API documentation states a readlen of 0 is valid so it doesn't make sense to warn the developer about that.

Blame indicates these lines are 8 years old (0701df6), so it was probably just overlooked, unnecessary developer safety net.

P.S. Great work on this library!!!! 🎉 🎉 🎉

Tested with FTDI FT2232HQ found in the Tigard

@eblot
Copy link
Owner

eblot commented Aug 14, 2025

Sorry for the delay.

It seems legit, but it is missing some unit test cases to validate it

@eblot
Copy link
Owner

eblot commented Aug 14, 2025

See 42efd8e (rebase/resolve)

@bhass1
Copy link
Author

bhass1 commented Aug 14, 2025

See 42efd8e (rebase/resolve)

Just reviewed it, it looks good. Do you want me to create a new PR based on that?

Let me know whether you want some unit testing from me?

@eblot
Copy link
Owner

eblot commented Aug 14, 2025

Let me know whether you want some unit testing from me?

It would be very nice if you could add some test with a basic I2C device to pyftdi/tests/i2c.py to be sure it does not break existing features. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants