Py_DEPRECATED should account for Py_Limited_API

Feature or enhancement

Proposal:

Take the example of Py_SetPythonHome().
It has been deprecated in 3.11, and we should now do things with PyConfig (added in 3.8).
But it is also part of the limited API. So it should not actually disappear, and someone building with Py_Limited_API<3.8 does not have the available symbols to use the non deprecated variant.
So every developer building with the limited API that cares about the warning will have to study each deprecated function, and if the non deprecated vairant is not in the stable API, add local deprecation warning disable code.

The proposal:
When Py_LimitedAPI is defined, Py_Deprecated should not trigger a warning if The deprecation version is greater than the limited API version selected by the macro (3.2 if the macro is empty, otherwise, the version value in Py_Limited_API), since we are really compiling for a lower version of python

I can probably do the PR myself if it is accepted

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Commencez par localiser les définitions et les utilisations de Py_DEPRECATED et Py_Limited_API dans les en-têtes de CPython, puis suivez la déclaration de Py_SetPythonHome comme exemple concret. Vérifiez comment la version de limited-API sélectionnée affecte les avertissements de dépréciation, et vérifiez que les avertissements ne sont supprimés que lorsque le remplacement n'est pas disponible dans cette version de l'API.