Documentation build overview

📚 pep-previews | 🛠️ Build #32784693 | 📁 Comparing a641dc2 against latest (c1f8b92)

  🔍 Preview build  

There was one minor comment:

There is one relatively minor point that should be clarified when transferring the specification into the official standards documentation. The PEP states:

If a field is present in both places, then the build backend is allowed to insert entries into the list or table, but not remove entries, reorder entries, or modify the entries.

This does not put any restrictions on where entries may be inserted - at the start, at the end, or in the middle. In practice, none of the existing fields affected by this PEP assign any meaning to ordering, so this doesn’t matter, but in order to avoid confusion should a future PEP add an order-dependent field, the specification should be explicit. Allowing insertions either anywhere, or just at the end, is fine with me - I’ll leave it to the PEP author to choose.

I think that means the PEP can be accepted as is, then when updating the spec at packaging.python.org this needs to be clarified, and a note is not needed here, but happy to add one if preferred. I think we have picked one, but I rather want to look at what it affects over the next couple days when preparing implementations before settling one one vs. the other.