Are you sure about that? The API itself is not deprecated, we're just changing it. I'm not sure what's the recommended practice here.

Yeah, I know what you mean. I feel like ideally this notice would be phrased along the lines of "X behaviour/practice is now deprecated" rather than "a DeprecationWarning is now emitted". That would be more to-the-point, and it would also work more naturally with this directive (X behaviour/practice is deprecated in 3.12, and will be removed entirely in 3.14).

But I was struggling to come to with a concrete suggestion for how to reword these notices :/

(The whatsnew and NEWS entries look great btw, it's just the notices in the API docs that feelslightly clunky to me)

I feel like ideally this notice would be phrased along the lines of "X behaviour/practice is now deprecated" rather than "a DeprecationWarning is now emitted". That would be more to-the-point, and it would also work more naturally with this directive (X behaviour/practice is deprecated in 3.12, and will be removed entirely in 3.14).

Yes, but documented as deprecated and emitting aDeprecationWarning are similar, but not equal, things 🙂 With the former, we don't need to emit a warning in the code.

To your original question, btw: I think it's pretty standard to use.. deprecated or.. deprecated-removed, even if it's just a particular usage of an API, rather than the API itself. See e.g.https://docs.python.org/3.12/library/asyncio-policy.html#asyncio.DefaultEventLoopPolicy, where the directive is used even though the class itself hasn't been deprecated at all; or#19867, which deprecated just a specific parameter; or lots of other examples in our docs 🙂

Aight! I'll try to reword it.

I've updated it to usedeprecated-removed, and I put in an extra line regarding what happens in 3.14. I'm too tired to reword the text 🙂