You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When thumby.py imports thumbyHardware.py, it exposes IDPin.
This is likely a typo and should be HWID. There is no reason to make IDPin accessible through the API.
Affects both lib and lib-emulator versions (here & here).
The text was updated successfully, but these errors were encountered:
Follow-up question: if HWID is available, should i2c and spi be accessible through the API? Why is it required to be exposed to third-party code? Should this be part of thumbyGraphics.py where initiation is self-contained just importing HWID (here).
None of the software we've ever seen actually uses the ID pin, so I'm fine with deprecating it. We just need to de-duplicate HWID-getting code inside of main from thumbyHardware, and then we can get the HWID straight from thumbyHardware and remove the import. I'll do this soon.
When
thumby.py
importsthumbyHardware.py
, it exposesIDPin
.This is likely a typo and should be
HWID
. There is no reason to make IDPin accessible through the API.Affects both
lib
andlib-emulator
versions (here & here).The text was updated successfully, but these errors were encountered: