On Thu, 13 Jun 2019 at 01:59, Steve Dower <steve.dower@python.org> wrote:
As Jeroen suggested, I think it's not just okay but a *good* thing for PyCFunctionObject to not have to refer back to the PyMethodDef. I've certainly run into this problem before.
We can still use PyMethodDef as the input value, but unless we have a particular public API for retrieving it (which I don't recall we do), it may as well just go away at that point.
My guess is it made perfect sense when everything was static, but no longer does now.
+1 - I think these cases can be treated as bugs where the introduction of the stable ABI invalidated old assumptions, but we haven't flushed out and fixed all those outdated assumptions yet.
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia