And does it matter to them? We handle/close issues based on whether a volunteer wants to work on them. IMO, PEP-11 is mostly a summary of what we want to work on, written for Python devs/triagers – so that you know who to bug for a particular platform, or whether you should “revert first and fix later” when something goes red.
For users, there’s very little actionable information in PEP-11.
Trouble is, they did come forward, and asked what they should do to help support a platform. We have no good answer. And that’s fine, really – it’s OK to do what seems best, and only standardize after it happens a few times. But we should probably acknowledge that Emscripten is in this experimental phase, and do what’s best for it rather than take PEP-11 too literally (and amend it whenever a detail needs changing).
(Sorry for hijacking the thread to talk about the bigger picture. The proposed change is a definite improvement.)