gh-92308: Add Pending Removal section to 3.11 What's New by erlend-aasland · Pull Request #92309 · python/cpython

Not so much about the lead, but about the content of the bullet point which can't really be distilled to a single name.

The "short" name could be "numeric literals immediately followed by a keyword", and then you can expand on it:

Numeric literals immediately followed by a keyword. Currently Python accepts expressions like 0in x, 1or x, 0if 1else 2, or [0x1for x in y] (which is ambiguous because it can be interpreted as [0x1 for x in y] or [0x1f or x in y]). Starting in this release, a deprecation warning is raised if the numeric literal is immediately followed by and, or, in, is, if, else or for. In future releases it will be changed to syntax warning, and finally to syntax error.


This "numeric literals followed by keyword" deprecation doesn't have a removal version, so would belong in a TDB/future section:

We could also try to enforce a target release for removal, even if it ends up being postponed. This will also make it easier to track deprecations. I also (half-jokingly) suggested to deprecate the deprecated directive in favor of deprecated-removed.

In the meanwhile, a TBD/Future section works.