@larry The Python Steering Council is ready to officially accept PEP-649. How’s the implementation looking? Do you think an implementation could land in time for 3.12beta1?
Based on the poll results in Survey: Should PEP-649 implementation use another future import? we’d prefer to go without a new from __future__ import co_annotations as the PEP lays out and just change the default behavior.
(Understanding that feedback during people’s beta period testing could change our minds on the __future__ topic.)