[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

2013-01-27 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- 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

2013-01-26 Thread Stefan Behnel
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 rep...@bugs.python.org

[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

2010-07-11 Thread Reid Kleckner
Reid Kleckner r...@mit.edu 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

[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

2010-07-06 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk 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 rep...@bugs.python.org

[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT

2009-12-25 Thread Ronald Oussoren
New submission from Ronald Oussoren ronaldousso...@mac.com: 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