-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove stop kwarg from busio.I2C().writeto #2082
Comments
It will be removed from libraries and then from here. See adafruit/circuitpython#2082 for details.
We're looking for any assistance in testing all of the outstanding library PRs associated with this issue! If you have any of these sensors and would like to help out, please grab something like a Feather M4 Express and do the following:
If you have any questions, please tag me in a comment or find me on Discord in the #circuitpython channel. Thanks! |
writeto_then_readfrom has been added to do a write -> no stop -> repeated start -> read sequence. This is done to match the capabilities of Blinka on Linux. Code that uses stop=False will not work correctly on Blinka. To fix, if stop=False then use writeto_then_readfrom otherwise use writeto then readfrom_into. First step in #2082
All library PRs have been merged. Changes were tested with LIDARLite to verify changes work successfully. |
Hello, this change send to have broken some stuff. More info here adafruit/Adafruit_CircuitPython_VL6180X#7 |
This has broken:
|
The stop kwarg was removed a couple of years ago. See here: adafruit/circuitpython#2082
With the introduction of
writeto_then_readfrom
into busio.I2C in 5.x. The stop kwarg is no longer needed. In fact, using it is likely the wrong thing to do since it is unsupported with Blinka.The text was updated successfully, but these errors were encountered: