I suspect we will grow a “language grammar” team for this purpose. It could grow to be larger than the others but I don’t think too many people would want all the work that comes with being on a team. I am already listing the expectation of timely basis for response and code review. I need to make that more explicit.
As I say in the document, for a PEP to enter FCP, all team members need to sign off on it. In other words, the team has to be unanimous about the change being ready. Otherwise it doesn’t get past the “summary comment”.
Remember I’m stating that all community members need to be enabled to comment on the proposal so those voices should appear in the summary comment. This means you don’t have to be on the respective team to be able to influence the process.
Now, before I comment on PEP 572, I’d like to make clear I make no specific judgment here on whether it’s a good feature to have. I am discussing the consensus for it, which we did not achieve as a community.
Without further ado, in case of PEP 572 specifically, the experts would probably not be unanimous on this one. And even if they were, due to the rather substantial general commiter and community backlash for the proposal, they would need to take into account a potential PEP rejection by vote. Since it’s a heavy hammer, they would probably not risk it.
With PEP 8012 in place, we are unlikely to have another outlier like PEP 572 accepted.