rpi with sysfs: pin.high() not working when running script with sudo

[ramalho]

rpi with sysfs: pin.high() not working when running script with sudo

[Vido]

Well,
I had some random: IOError [Errno 16] Device or resource busy
But IOError: [Errno 1] Operation not permitted, had never happend to me, specially on sudo.

I guess our /sys/class/gpio implementation looks quite weak and unstable.
Perhaps it is time to move to RPi.GPIO, or give the good-old C a shoot.

[ramalho]

I still think we should insist with sysfs a little more. I was not very
focused yesterday, and even if RPi.GPIO is better (it probably is), sysfs
is a standard across many boards and we should make it work because
sometimes compiling a C extension in one of these boards is going to be
difficult. We just need some time to code it carefully. For example, it
makes not sense to export all pins if the app will only use a few. And then
we must keep track of which were exported so that only those are
unexported. And we need to improve our tests. Do you know py.test? I want
to start using that. doctest is good to demo/teach the straightforward
cases, for anything else unittest is better and py.test even more.

On Sun, Apr 6, 2014 at 2:05 AM, Lucas Vido [email protected] wrote:

Well,
I had some random: IOError [Errno 16] Device or resource busy
But IOError: [Errno 1] Operation not permitted, had never happend to me,
specially on sudo.

I guess our /sys/class/gpio implementation looks quite weak and unstable.
Perhaps it is time to move to RPi.GPIO, or give the good-old C a shoot.

—
Reply to this email directly or view it on GitHubhttps://github.com/garoa/pingo/issues/5#issuecomment-39658698
.

Luciano Ramalho
Twitter: @ramalhoorg

Professor em: http://python.pro.br
Twitter: @pythonprobr

[ramalho]

For now we have decided to use RPi.GPIO on the Raspberry Pi, instead of sysfs