[issue35616] Change references to '4.0'.

Emmanuel Arias added the comment: Hello! IMHO I don't think is good say that they will remove on a version that is not planned yet. I agree with Marc-Andre is better say " they will be remove in the next major release" -- ___ Python tracker <

[issue35616] Change references to '4.0'.

Marc-Andre Lemburg added the comment: Why not change the wording to read "... will be considered for removal in the next major Python release". Note that removal of Py_UNICODE APIs will not only break compatibility with Python 2, but also with the early Python 3 releases. And please also co

[issue35616] Change references to '4.0'.

STINNER Victor added the comment: > One or two versions after using Py_DEPRECATED for all deprecated functions > (but not earlier than EOL of 2.7) we can make them issuing run-time warnings. Maybe we can experiment adding warnings only in development mode, when python3 -X dev is used? > I'm

[issue35616] Change references to '4.0'.

STINNER Victor 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 wa

[issue35616] Change references to '4.0'.

Terry J. Reedy added the comment: After reading Serhiy's explanation, I agree that '4.0' is better than a specific '3.nn'. I did not realize how much was still left to be done. We can revisit this when there is a definite removal date. A literal 'sometime' might be better, but not worth a

[issue35616] Change references to '4.0'.

Serhiy Storchaka added the comment: Removing the C API function is a major breaking change. AFAIK there was no precedence since 3.0. It may be that we will name the new version 4.0 after doing this. In any case, first than remove this API, we need to pass the following steps: * Implement Py

[issue35616] Change references to '4.0'.

Emmanuel Arias added the comment: Same similar occur with other docs $ git grep 'deprecated-removed::.*4\.0' Doc/c-api/arg.rst: .. deprecated-removed:: 3.3 4.0 Doc/c-api/arg.rst: .. deprecated-removed:: 3.3 4.0 Doc/c-api/arg.rst: .. deprecated-removed:: 3.3 4.0 Doc/c-api/arg.rst: .. de

[issue35616] Change references to '4.0'.

Change by Emmanuel Arias : -- keywords: +patch, patch, patch pull_requests: +10688, 10689, 10690 stage: needs patch -> patch review ___ Python tracker ___ _

[issue35616] Change references to '4.0'.

Change by Emmanuel Arias : -- keywords: +patch, patch pull_requests: +10688, 10689 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue35616] Change references to '4.0'.

Change by Emmanuel Arias : -- keywords: +patch pull_requests: +10688 stage: needs patch -> patch review ___ Python tracker ___ ___ P

[issue35616] Change references to '4.0'.

New submission from Terry J. Reedy : https://docs.python.org/3/c-api/unicode.html#deprecated-py-unicode-apis says "Deprecated since version 3.3, will be removed in version 4.0." (I am aware that the quote above was written before we decided that '3.9' should be followed by '3.10' rather than '4.