Open WayneKeenan opened 7 years ago
For the i2c fallback nobody would want piconzero to depend on picraftzero.thirdparty.mocks.raspiberrypi.rpidevmocks
or the rpidevmocks
PiCraftZero uses.
Perhaps piconzero could do it's default behaviour unless an optional i2c_provider
option was passed to the constructors/init or a module global?
Hi, this is more of a query and perhaps start of a discussion.
I've embedded a modified version of the piconzero library in PiCraftZero.
I've included a diff below to highlight the details but it's not intended as a PR or patch, it's just for illustration purposes. Also, my version has fallen behind the GitHub one.
In summary the tweaks are:
init
more than once is a no-opIt would be nice to get these into the piconzero library in some way instead of users having to import from the namespace my modified version exists in.
The diff: