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 pablogsal
Recipients Dennis Sweeney, Guido.van.Rossum, Mark.Shannon, Yonatan Goldschmidt, ammar2, chris.jerdonek, corona10, erlendaasland, gvanrossum, hauntsaninja, pablogsal, petr.viktorin, rhettinger, serhiy.storchaka
Date 2021-05-11.13:05:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In any case, if we decide to let it stay, at the very least this behaviour (that these functions are not stable) needs to be documented everywhere: what's new, C-API docs...etc And probably we need to somehow add it to the future deprecations of 3.10 for visibility.

As I mentioned, I simphatise with your argument and I think it makes sense, but we cannot just do it in a BPO issue, I'm afraid.
Date User Action Args
2021-05-11 13:05:37pablogsalsetrecipients: + pablogsal, gvanrossum, rhettinger, petr.viktorin, chris.jerdonek, Mark.Shannon, serhiy.storchaka, Guido.van.Rossum, ammar2, corona10, Dennis Sweeney, erlendaasland, Yonatan Goldschmidt, hauntsaninja
2021-05-11 13:05:37pablogsalsetmessageid: <>
2021-05-11 13:05:37pablogsallinkissue40222 messages
2021-05-11 13:05:37pablogsalcreate