Your quote only refers to a small part of the deprecations, i.e. deprecated type aliases. Deprecations that are not in that group do cause warnings, and some of them are already scheduled for removal.

Your quote also conveniently left out the following paragraph:

> The aliases are guaranteed to remain in the typing module without deprecation warnings until at least Python 3.14.

Python 3.14 is less than a year away.

> Even if they decide to remove these at some point, you're looking at several years before it actually happens, and you'll have plenty of time to migrate.

I agree. I still think it adds to the pile of chores, especially for people who are on the fence anyway as to whether type annotations are worth the additional mental load to them.