PEP 600: add manylinux2014 compatibility

[mayeut]

• Add a link to PEP 599
• Add a mention to manylinux2014 aliases

c.f. discussion for more details

[mayeut]

Not sure if/how the fact that an update was made should be reflected in the PEP given it's not Final/Active.

[pfmoore]

I'm not going to be able to monitor this PR or the associated discussion. Please @-ping me explicitly when the three PEP authors have confirmed they are OK with this change.

[mayeut]

@njsmith, @takluyver, @di,

gentle reminder: can you review this per Paul's comment. Thanks

[mayeut]

@njsmith, @takluyver,

gentle reminder: can you review this per Paul's comment. Thanks

[takluyver]

I'm sorry for the delay!

I think @mayeut is currently much more involved with the manylinux machinery and definitions than I am. Perhaps PEPs, like packages, should have 'authors' and 'maintainers'. 🙂

[takluyver]

(And now I got the wrong radio button...)

[pfmoore]

Thanks @takluyver! Normally PEPs don't get substantive updates after they are published, so this isn't typically a big deal. It would probably be useful to move the specification out of the PEPs, and into https://packaging.python.org/specifications/platform-compatibility-tags/. That would also mean maintenance could be handled outside of the PEP repo.