tags 856413 +pending
tags 919617 +patch +pending
tags 919620 +patch +pending
thanks
I have now prepared a NMU for gpiozero addressing bugs 856413, 919617 and
919620.
I have uploaded this NMU to delayed/10. A debdiff is attatched to this mail
(really attatched this time, sorry).
Please tell me i
tags 856413 +pending
tags 919617 +patch +pending
tags 919620 +patch +pending
thanks
I have now prepared a NMU for gpiozero addressing bugs 856413, 919617 and
919620. I have uploaded this NMU to delayed/10. A debdiff is attatched to this
mail.
Please tell me if you see any issues with this NMU
tags 856413 +patch
thanks
As part of preparing for opening up the architecture lists for gpiozero I
researched what there is in the way of raspberry pi detection.
If no backend is explicitly specified gpiozero tries the following four
backends in-order. 'rpigpio', 'rpio', 'pigpio', 'native'
'
I have chatted with Dave Jones (waveform80) about getting gpiozero support on
more architectures. It seems sensible that as part of doing this we also
package pigpio to support remote gpio operations.
Dominik do you mind if I add myself to the uploaders for this package and work
on updating it
Thanks Nick
Please could you make gpiozero available for all arches?
>
I don't believe any changes to the library would be required for this. The
control file
already states "Architecture: all" [1]. Is that correct, or is there
anything else required?
[1]
https://github.com/RPi-Distro/python-gpi
I'm currently packaging Mu [1] and its missing dependencies for
Debian, and the question of remote GPIO pin control has arisen.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901461
Mu declares gpiozero and pigpio as dependencies. gpiozero can be used
with pigpio on a remote system to co
When run on a Raspberry Pi, the gpiozero module uses a low-level gpio pin
library to do the physical pin state manipulation on the hardware.
When run on a PC, you can either:
- use the mock pin implementation for testing purposes
- use the pigpio python library to access real hardware pins on a r
> could you please provide a mock implementation of gpiozero python module
> on all Debian architectures?
To clarify that:
gpiozero already *has* a mock implementation.
This bug asks for enabling the build on all architectures so this mock
implementation becomes available on non-ARM platforms.
> Can you explain the motivating use-case please?
See https://lists.debian.org/debian-python/2017/02/msg00073.html .
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-georg
Hi Michael
> Can you explain the motivating use-case please?
A fake implementation on all architectures can be useful for testing
purpose without having to rely on an emulator.
Can you explain the motivating use-case please?
On Tue, Feb 28, 2017 at 7:33 PM, Simone Rossetto wrote:
> Package: gpiozero
> Severity: wishlist
>
> Dear Maintainer,
>
> could you please provide a mock implementation of gpiozero python module
> on all Debian architectures?
>
>
> Thanks
> Simone
Package: gpiozero
Severity: wishlist
Dear Maintainer,
could you please provide a mock implementation of gpiozero python module
on all Debian architectures?
Thanks
Simone
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (12, 'unstable')
12 matches
Mail list logo
