Skip to content

Conversation

@jeanas
Copy link
Contributor

@jeanas jeanas commented Nov 14, 2023

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/

@jeanas
Copy link
Contributor Author

jeanas commented Nov 14, 2023

@ofek

Copy link
Contributor

@willingc willingc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jeanas

@willingc willingc added this pull request to the merge queue Nov 14, 2023
Merged via the queue into pypa:main with commit a081a11 Nov 14, 2023
@jeanas jeanas deleted the pep723 branch November 14, 2023 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants