[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

Changes by Serhiy Storchaka : -- resolution: -> duplicate stage: patch review -> committed/rejected status: open -> closed superseder: -> PyModuleDef_HEAD_INIT does not explicitly initialize all fields of m_base ___ Python tracker

[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

Stefan Behnel added the comment: This is a duplicate of issue 9518 (or the other way round) and should be closed as fixed in 3.2. -- components: +Extension Modules nosy: +scoder ___ Python tracker _

[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

Reid Kleckner added the comment: This patch looks good to me, after digging through the relevant module code. I was confused though for a bit as to why PyModuleDef is a PyObject with a NULL type. It turns out that import.c wants to keep them in a dictionary, so it needs to be able to cast to

[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

Mark Lawrence added the comment: This is a miniscule patch to moduleobject.h could someone with the relevant knowledge please review it, thanks. -- nosy: +BreamoreBoy ___ Python tracker ___

[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

New submission from Ronald Oussoren : When running GCC with warnings the compiler can warn about incomplete structure initializers. This gives spurious warnings when initializing a PyModuleDef structure using PyModuleDef_HEAD_INIT The attached patchs changes PyModuleDef_HEAD_INIT to explicitly