➜

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 lukasz.langa
Recipients iritkatriel, jdemeyer, lukasz.langa, pablogsal, petr.viktorin
Date 2021-08-27.10:48:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630061332.65.0.740335610012.issue44874@roundup.psfhosted.org>
In-reply-to
Content 
This isn't closed yet because we need a decision whether to issue warnings about Py_TRASHCAN_SAFE_BEGIN/END usage in 3.10 as well. This was suggested by Petr here:
https://mail.python.org/archives/list/python-dev@python.org/message/KWFX6XX3HMZBQ2BYBVL7G74AIOPWO66Y/

I personally don't feel like it's worth going any further than 3.10: Python 3.8 is security fixes only at this point, we haven't received any reports from users about the breakage in 3.9 so far with 3.9.7 around the corner.

So the backport is up to Pablo: should we raise the compiler warning on 3.10 as well?
History
Date User Action Args
2021-08-27 10:48:52lukasz.langasetrecipients: + lukasz.langa, petr.viktorin, jdemeyer, pablogsal, iritkatriel
2021-08-27 10:48:52lukasz.langasetmessageid: <1630061332.65.0.740335610012.issue44874@roundup.psfhosted.org>
2021-08-27 10:48:52lukasz.langalinkissue44874 messages
2021-08-27 10:48:52lukasz.langacreate