Have you thought about caching the state on Connection objects? That way you could get the state from a cursor by following two pointers. (And similarly for other cases where you have a Connection, which is most of pysqlite).
Connections are already quite heavy, so adding one more pointer might be a good trade-off.

pysqlite_get_state_by_cls looks like it'll eventually use_PyType_GetModuleByDef, which isn't as fast as following two pointers.

Have you thought about caching the state on Connection objects? That way you could get the state from a cursor by following two pointers. (And similarly for other cases where you have a Connection, which is most of pysqlite).
Connections are already quite heavy, so adding one more pointer might be a good trade-off.

Yes, I have though about it, but I don't remember why I didn't follow that idea :) As you say, it's probably a very good trade-off. I'll have a go at it.

pysqlite_get_state_by_cls looks like it'll eventually use_PyType_GetModuleByDef, which isn't as fast as following two pointers.

Both true. No, it was meant to usePyType_GetModuleState.

PTAL!

Looks good, I just did a trivial merge to resolve a conflict.

@erlend-aasland: Status check is done, and it's a success ✅ .

Looks good, I just did a trivial merge to resolve a conflict.

Great, thanks and thank you for reviewing.