Infra: Use PEP abstract/introduction as HTML and OG description #3801
Conversation
This file contains 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
|
I'll merge this tomorrow, if no reviews or objections. |
pradyunsg
reviewed
Jun 11, 2024
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.
Fixes #2919.
Use the PEP abstract for
<meta property="og:description">and<meta name="description">.If the abstract is not found, use the introduction. If that's not found, use the current default of "Python Enhancement Proposals (PEPs)".
The abstract and intros cover 631 / 652 PEPs, which is good enough.
(The abstract alone covers 594 / 652, which might be enough to remove a few extra lines here?)
Trim the description to 256 characters, and escape things like double quotes.
📚 Documentation preview 📚: https://pep-previews--3801.org.readthedocs.build/