Phil Thompson <p...@riverbankcomputing.com> added the comment:
On 19/07/2019 11:37, Jeroen Demeyer wrote: > Jeroen Demeyer <j.deme...@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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37588> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
