Message 393456 - Python tracker

Message393456

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 <1620738337.64.0.0952405896782.issue40222@roundup.psfhosted.org>
In-reply-to
Content
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.
History
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: <1620738337.64.0.0952405896782.issue40222@roundup.psfhosted.org>
2021-05-11 13:05:37pablogsallinkissue40222 messages
2021-05-11 13:05:37pablogsalcreate