This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author methane
Recipients ZackerySpytz, jdemeyer, methane, philthompson10
Date 2019-07-19.09:50:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1563529840.96.0.422101757725.issue37588@roundup.psfhosted.org>
In-reply-to
Content
> I am not "touching" tp_print. I am simply defining it as 0 to avoid the missing initialiser warning.

I meant it.  `tp_print = 0` touches the deprecated `tp_print` field.
It is not forward compatible.  Note that we need to re-add tp_print only for C code which does `tp_print = 0`.


>  My point is that it should be possible to write code that doesn't trigger warnings (whether or not you suppress them).

There is a simple solution: don't use `-Wextra`.

We have some reserved/deprecated/unused fields.  Setting 0 to them makes forward incompatible code.  It bothers us to remove or reuse these fields.

There are some other solutions, suppress the missing initializer warning as I wrote above, or use PyType_FromSpec instead of static type.
History
Date User Action Args
2019-07-19 09:50:41methanesetrecipients: + methane, philthompson10, jdemeyer, ZackerySpytz
2019-07-19 09:50:40methanesetmessageid: <1563529840.96.0.422101757725.issue37588@roundup.psfhosted.org>
2019-07-19 09:50:40methanelinkissue37588 messages
2019-07-19 09:50:40methanecreate