-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support for use as a drop-in replacement for RPi.GPIO for gpiozero #10
Comments
In particular, to be a drop-in replacement, there would need to be a "pin factory" implementation, which normalises the functionality of a pin library into a standard set of methods. The RPi.GPIO one is here: https://github.com/gpiozero/gpiozero/blob/master/gpiozero/pins/rpigpio.py More info: https://gpiozero.readthedocs.io/en/latest/api_pins.html |
A test-driven way we could approach this feature would be to integrate a version of that file into our testing system as we move towards API-equivalence with RPi.GPIO. |
Nice, I'll try to have a look at it this weekend (if I remember!) 👍 |
Oops, looks like I forgot another constant:
|
Alright it imports correctly now, but gpiozero now throws the following when I try to evaluate PiFactory.pi_info()
|
Are you able to get the revision code another way? We ought to patch that. @lurch any ideas for doing that outside of Raspbian? |
mistakenly closed instead of #37 |
About to look into revision code issue. Just released RPi.GPIO2 0.3.0a2 to PyPi so people can |
On one of the pigpio issues: joan2937/pigpio#340, |
One way to do might be to have a table mapping values of
|
Using this patch to gpiozero, I was able to get gpiozerocli.pinout.main() to work with RPi.GPIO2 0.3.0a2 |
In response to: gpiozero/gpiozero#840
The text was updated successfully, but these errors were encountered: