➜

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 philthompson10
Recipients ZackerySpytz, jdemeyer, methane, philthompson10
Date 2019-07-19.11:47:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <7506aaac11f4c047495da8ed6d682a32@riverbankcomputing.com>
In-reply-to <1563532652.24.0.531159105825.issue37588@roundup.psfhosted.org>
Content 
On 19/07/2019 11:37, Jeroen Demeyer wrote:
> Jeroen Demeyer <J.Demeyer@UGent.be> added the comment:
> 
>> We have some reserved/deprecated/unused fields.  Setting 0 to them 
>> makes forward incompatible code.
> 
> Good point. tp_print is removed in 3.9

Which is why I protect the initialisation with #if PY_VERSION_HEX < 
0x03090000

As far as I can see this is the "right thing" to do. However doing the 
"right thing" means I cannot avoid warnings without resorting to 
compiler-specific build system changes.

With the change I am asking for I can suppress the warning (because I 
have explicitly dealt with the issue) in the code itself without 
affecting the rest of the system.
History
Date User Action Args
2019-07-19 11:47:12philthompson10setrecipients: + philthompson10, methane, jdemeyer, ZackerySpytz
2019-07-19 11:47:12philthompson10linkissue37588 messages
2019-07-19 11:47:11philthompson10create