Inada Naoki <songofaca...@gmail.com> added the comment:
> Which is why I protect the initialisation with #if PY_VERSION_HEX < 0x03090000 It is your specific case. We can not assume people do it, or even you never forget it. So this is not the "right thing" we can recommend to all users. Once you or other people suppress the deprecation warning and forget the protect, compatibility issue happen again. Why such dangerous option is needed? Note that we don't use `-Wextra` or `-Wmissing-field-initializers`. The missing initializer warning is specific to you. You manually enabled the warning. So why should we provide the way to suppress the warning we never recommend to enable? ---------- _______________________________________ 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
