Dave Malcolm dmalc...@redhat.com added the comment:
Forgot to close this one out
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9518
___
Changes by Dave Malcolm dmalc...@redhat.com:
--
stage: patch review - committed/rejected
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9518
___
Stefan Behnel sco...@users.sourceforge.net added the comment:
I agree that this is annoying, we get the same thing in Cython's test suite all
over the place. Any foreign warning that doesn't get triggered helps in
debugging your own code. And this one is easy to avoid.
--
nosy:
Antoine Pitrou pit...@free.fr added the comment:
This looks ok to me.
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9518
___
___
Dave Malcolm dmalc...@redhat.com added the comment:
Fix committed to py3k as r86499
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9518
___
___
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
the patch looks OK, but out of curiosity: do you really declare all the fields
of a PyTypeObject?
This structure is really designed so that newer members are left at the end;
most types don't need to initialize them, C standard ensures
Dave Malcolm dmalc...@redhat.com added the comment:
Thanks. The code in question is a wrapper to a security-sensitive library
(user-space SELinux code), hence the compilation warnings have been turned up
as much as possible.
The .c code in question is generated by SWIG, and that does indeed
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +loewis
versions: -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9518
___
___
Changes by Dave Malcolm dmalc...@redhat.com:
--
title: PyModuleDef_HEAD_INIT does not explicitly initial all fields of m_base
- PyModuleDef_HEAD_INIT does not explicitly initialize all fields of m_base
___
Python tracker rep...@bugs.python.org
