I'm a little confused as to why it hasn't been implemented for 3.13 yet. Did we forget this?

I think Larry didn't have time to push it through (and we're now at beta, so will need to wait for 3.14). Jelle and Łukasz have both said they'll ensure it gets done for 3.14.

OK, I've updated it to 3.14. Doesn't that mean the PEP also needs to be updated? It could be quite confusing to read it has been implemented in 3.13 when it hasn't.

cc @JelleZijlstra

This isn't entirely accurate, since from __future__ import annotations as originally written definitely will not become the default. However, I'm not entirely clear yet on what the end state will be; just posted about it at https://discuss.python.org/t/pep-649-deferred-evaluation-of-annotations-tentatively-accepted/21331/44.

I'll update this when a decision has been made.

@JelleZijlstra, does this look better? Or should be the Steering Council be mentioned in the note?
Should we also mention that it still works for the time being?

This wording is not great because the future fate of the future import is undetermined until PEP-749 is accepted, and because what you wrote makes it sound like the behavior of from __future__ import annotations is changing in 3.14 (it isn't). I haven't been able yet to come up with a good, concise alternative though.

Does this look better? from __future__ import annotations will either continue to work, become a no-op or be removed. It will never become the default.

I'm closing this. Could you assign yourself to the issue?