Quoting from https://docs.python.org/3.10/c-api/module.html:
"It is recommended extensions use other PyModule_* and PyObject_* functions rather than directly manipulate a module’s __dict__."

A number of modules still access the module dictionary directly:
zsh % grep -r PyModule_GetDict Modules
Modules/errnomodule.c:    PyObject *module_dict = PyModule_GetDict(module);
Modules/_sre.c:    d = PyModule_GetDict(m);
Modules/_cursesmodule.c:    d = PyModule_GetDict(m);
Modules/_threadmodule.c:    d = PyModule_GetDict(m);
Modules/signalmodule.c:    PyObject *d = PyModule_GetDict(m);
Modules/_xxsubinterpretersmodule.c:    PyObject *ns = PyModule_GetDict(main_mod);  // borrowed
Modules/_xxsubinterpretersmodule.c:    PyObject *ns = PyModule_GetDict(module);  // borrowed
Modules/socketmodule.c:    dict = PyModule_GetDict(m);
Modules/_ssl.c:    d = PyModule_GetDict(m);
Modules/_curses_panel.c:    PyObject *d = PyModule_GetDict(mod);
Modules/_sqlite/connection.c:    module_dict = PyModule_GetDict(module);
Modules/_winapi.c:    PyObject *d = PyModule_GetDict(m);
Modules/pyexpat.c:    d = PyModule_GetDict(m);

Are all these occurrences in the module initialization code?

I think there is nothing wrong with this. Yes, the code can be a little clearer if use PyObject_GetArrt or PyModule_Add*, but rewriting can introduce new bugs.

The remark in the documentation is rather about reading the module attributes and writing a new code. It does not require rewriting existing code.

You can do this, but it will be treated as pure cosmetic change. It can be accepted if the new code is much clearer.

> Are all these occurrences in the module initialization code?

Most of them, but not all.

> but rewriting can introduce new bugs.

Of course.


> You can do this, but it will be treated as pure cosmetic change. It can be accepted if the new code is much clearer.

It mostly results in more compact code, which, in my opinion, would improve both readability and maintainability.

I would leave it as-is.