Even a feature meant for core devs, who can use it to speed things up, could be a good PEP.
I’m picking on this PEP because:
- PEP 669 (Low Impact Monitoring) builds on it. I don’t think it shouldn’t build on a draft. (Also, hopefully a PEP for a change that’s used in another proposal is up-to-date – something I wouldn’t necessarily expect from a Draft/Informational text.)
- it looks like a good text to explain technical reasons behind the speedup in 3.11. IOW, it’s good for marketing :)
It looks like you wouldn’t object to moving it to Standards Track. Would you mind if I made the python-dev post and submitted to the SC?