"R.Wieser"  writes:
>> The relevant module is RPi._GPIO. That's what PyInit__GPIO is
>> setting up.
>
> That is not the part I have been talking about.
>
>> PyModule_AddObject gives the type defined in C by PWMType
>> the name "PWM" in that module.
>
> Neither is that
>
>> it doesn't know about the internals of PWMType, so it seems
>> to me that your preferences about who knows what are already met.
>
> You're playing games, implicitily declaring the PWMType object itself
> as not being internal to the PWM module/sourcefile.  I'm afraid that
> that doesn't quite work for me.

I’ve no idea what you think the game is. I’ve been assuming throughout
that ‘module’ meant a Python module, since we’ve been talking about a
Python module, rather than a C source file. If you want to use one word
to mean two quite different things, without even clarifying what you
mean, then I don’t think you get to tell other people that they are
playing games when they don’t realise you’re being ambiguous.

Based on your last code fragment it looks like all you’re now arguing
about is what name the type object should be referred to by when adding
it to the module, rather than where the PyModule_AddObject call is. That
falls into the “don’t care” camp for me (which is why I didn’t respond
to that bit).

--
https://www.greenend.org.uk/rjk/

--- SoupGate-Win32 v1.05