I think including the text of _get_musl_version from that PR into the PEP would be acceptable. I can’t comment on whether it’s the “right” approach, but I assume the MUSL experts in this discussion can let you know about that
PS As with PEP 600, I’m OK with being PEP-Delegate by default for this PEP on the basis that I’ll be looking at whether the discussion here looked sufficiently complete, and reached an acceptable compromise (I have no specialist MUSL knowledge). But if anyone wants to suggest someone who does know MUSL who would be better as PEP-delegate, feel free to speak up!
I added a code block to show how to retrieve the musl version. I chose to only briefly describe how to get the musl libc’s path from a Python executable, since the implementation is a bit too long to include in a document, but shouldn’t be too difficult to devise from reading the ELF spec (ref provided in the PEP).
Also note that there’s now a thread for the PEP, so it might be a good idea to move further discussions there so we can keep things in one place
