Dennis,

> There are NO internal tables...

Please re-read my definition of 'internal'.  That you have your own (which
you have not mentioned yet) should not be the basis of an argument.

> And no global conversion routine.

That I never even suggested.

> Tables and conversion are specific to the GPIO library one is using.

True.  Sow, how about that GPIO library exposing what it uses ?   So that
I/we can convert from one of its pinnaming schemes to its other one(s) ?

> And... if you intend your code to be used by others (via import and
> calling functions) you are going to have to document which library you
> are using, and for those where it matters, which pin naming structure you
> expect them to be using.

No.   I expect my code, if possible, to adapt to whatever the user wishes to
use, not the other way around.

> Again -- gpiozero SIMPLIFIES a lot of this...
[snip]

Actually, this is the fricking *first time* anyone has tried to tell me WHY
I should be using gpiozero over a RPi.GPIO, without just appearing to order
me to do so.

I'll most likely take a look at it.  ... after I've finished with what I'm
currently busy with.

> Set up your module on the basis that the end-user should initialize
> gpiozero with their preferred back-end, and everything else should
> be transparent.

Sounds good.  And thats all that I tried to do (for my class module using
RPi.GPIO) too.

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05