> On 18 Aug 2021, at 11:47, Irit Katriel <iritkatr...@googlemail.com> wrote: > > It remains the decide how to backport the compiler warning to older versions, > and to which versions.
3.8 is when the macros broke. Since they cause segfaults, I'd say that's a pretty good reason to backport the warnings. While 3.8 in security-only fix mode, I think there's no issue with showing the "pending" deprecation in the to-be-released 3.8.12. And if that, then 3.9.7, and 3.10.0rc2 as well. Of course, for the latter we need Pablo's confirmation. The additional argument for it is that we backported GH-27683 (using new macros in frameobject.c) all the way back to 3.8. So building Python itself shouldn't start raising the deprecation warnings itself. But if it does, we'll just fix that as well. - Ł
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/QTRAEXONS2I7ICWLH65IOMR6KITXZ6CP/ Code of Conduct: http://python.org/psf/codeofconduct/
