user-docs: import PEP 541 policy as a page #18793
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: William Woodruff <william@astral.sh>
|
Generally looks good to me, assigning to @Thespi-Brain for a deeper review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
From conversation in psf/policies#41 -- I've moved this into the PyPI user docs instead. I think the "project management" hierarchy is the best place for it, since we have similar policy-like stuff under it already (like quotas and yanking).
I've left the page verbatim from that other PR, which also means it doesn't really read exactly like the language in the other pages (it's more PEP-y). I wasn't sure how much I should edit it for style given that it's standard language 🙂
xref #17999 for additional context on what's motivating this.
CC @Thespi-Brain @ewdurbin @miketheman from the original PR