> They have been deprecated in C already. Compiler emits warning.

> This additional proposal is adding runtime warning before removal.

Oh, sorry. I misunderstood the previous statement then. In that case, I think scheduling the removal for 3.11 is perfectly reasonable if the compiler warnings have already been in place. +1.

On Sat, Jun 13, 2020 at 7:20 AM Inada Naoki <songofacandy@gmail.com> wrote:

2020年6月13日(土) 20:12 Kyle Stanley <aeros167@gmail.com>:
> Additionally, raise DeprecationWarning runtime when these APIs are used.

So, just to clarify, current usage of these 7 unicode APIs does not emit any warnings and would only start doing so in 3.10?

They have been deprecated in C already. Compiler emits warning.

This additional proposal is adding runtime warning before removal.

In this case, it might be okay to remove in 3.11 since they've been deprecated for an exceptionally long period and appear to have a clear transition path. But, 3.12 would be safer for removal, and I don't think it would be much of an additional burden on our end to keep them around for one extra version.

I am trying to find and remove use of theses APIs in PyPI packages.
We will postpone the removal if the migration is slow.
But let's set the goal to 3.11 for now.