GPIO.setmode(x) missing

[ericvrp]

GPIO.setmode(x) is missing. It should be either a dummy function or it should do something meaningful.

Currently when 'P8_10' or 'GPIO0_10' is for instance used. with GPIO.setmode(BOARD or BCM) the additional syntax of using integer 10 could be mapped to either P8_10 or GPIO0_10 .

[jwcooper]

I'm not sure about this one. What is the necessity of setmode if the key and name are already offered as options dynamically? Is it just to match the RPi.GPIO methods? If I do add it, I think it would be a dummy implementation to help with porting code. Although, I think it would be just as easy to remove it if you're porting code from RPi though, as you'd still need to change all your channels.

The issue is that there are also other integers that are already mapped to P8_10. For example, that particular pin has gpio number 68. It isn't a very user-friendly mapping. Also, using 10 for P8_10 could be confused as 10 for P9_10. The issue is the large number of pins available compared to the Pi. :)

I'm going to close this for now, but would be open for further arguments on it.

[ericvrp]

I don't want to re-open it but it's a good discussion subject nonetheless. I see the points you are making. To answer your question: it's for compatibily purposes indeed. In my program I would like to use the same codebase for RPi and BBB so that I only need to change some port number/names in a config.py file. At the moment the importing port looks like this:

try:
....import RPi.GPIO as GPIO #Raspberry Pi
except ImportError:
....import BBIO.GPIO as GPIO #Beaglebone Black
....GPIO.BCM = None
....GPIO.setmode = lambda x: None

Which is no big problem but perhaps it would be better placed in the library.