Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resembles #1372, #1340 and #1337.
Like those other PRs, it has one first commit importing the PEP text verbatim, and a second commit changing it. This is so that reviewers can see exactly what changed (content explaining the motivation and alternatives is trimmed, and some references are adjusted).
I'm fully aware that PEP 723 was only provisionally/conditionally accepted. I'd still like to have it in the PUG so that if/when it becomes accepted, all the announcements can read "Tool X now supports inline script metadata" instead of "Tool X now supports PEP 723". I guess it's clear by now that I don't like concepts referred to by PEP number 😉
The provisional status is clearly reflected in the text.
📚 Documentation preview 📚: https://python-packaging-user-guide--1388.org.readthedocs.build/en/1388/