Hi,
I am writing this message on behalf of the Steering Council.
The Steering Council has discussed this in one of the recent meetings. Although we have to say that we are very unhappy that this happened, after discussion with the release management team, the Steering Council have decided not to revert these changes in 3.11 to not affect the stability of the release as at the time this was discussed, the 3.11 branch was already in release candidate 1.
This doesn’t mean that the SC thinks this outcome is ok. We want to emphasise that this outcome is not acceptable, and neither is the way this was done. Changes that require a PEP should never be included in a stable branch before the PEP is done and if they ever land in one of the supported branches without the backing PEP, they should be reverted immediately.
The Steering Council would like to remind everyone that respecting the process is fundamental to a good working environment in the core development team and failing to do so not only makes Python less stable but can also affect the perception of users on the project and its will also make life more difficult to other core devs and colleagues.
Thanks for your understanding.
In the name of the Steering Council,
Pablo Galindo Salgado