[issue35616] Change references to '4.0'.

[STINNER Victor]

STINNER Victor <vstinner at redhat.com> added the comment:

I disagree. It's acceptable to break the C API in a minor release if the change has been properly promoted, documented, announced, etc.

IMHO breaking the C API in 4.0 is going to send a bad signal to users.

Multiple core developers asked multiple times to wait until Python 2 is really dead before removing some features which are used on Python 2 and Python 3. So at least, we must wait until January 1st, 2020, before removing Py_UNICODE APIs.

I also would like to see the deprecation warning supported on Windows.

I didn't see any announcement of future removal of C API on the capi-sig mailing list.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35616>
_______________________________________