``check-peps`` codifies the rules in PEP 1 and PEP 12 into a single
place containing all of the PEP-specific checks. These are primarily
header and metadata validation, and ensuring that direct links to
RFCs and PEPs aren't used.
Reviewed-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Reviewed-by: C.A.M. Gerlach <cam.gerlach@gerlach.cam>
* Lint: Only ignore per-message links in Post-History with trailing slash
* PEP 684: Add trailing slash to per-message Post-History link
* Infra: Use clearer term (message, not post) for single Discourse messages
* Use #121212 for dark theme bgcolor
* Use #1111111 for dark theme bgcolor
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
Since inversion doesn’t just affect brightness, but also hue, there’s a problem: Some background colors have perceptually less contrast with their text when hue rotated. This rotates their hue back, fixing the contrast issue.
* Update headers/etc. of older packaging PEPs to reflect replacement PEPs
* Infra: Fix lowercase and tweak plural in text for PyPA spec banner
* Add banner to all relevant PEPs pointing to their canonical PyPA specs
Co-authored-by: Brett Cannon <brett@python.org>
Release PEPs are a pretty unusual kind of PEP and it's useful to me to have
them all listed together. Happy to adjust the name of the topic if desired.
I took the opportunity to adjust the status of a few release PEPs. Now all
releases for EOL versions are Final (3.5 was previously Active), and all
releases for released versions are Active (3.10 was still draft). 3.11 remains
Draft as 3.11 has not yet been released.
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
* PEP 555, 653: Fix inline literal missing (escaped) space after literal
* Add newline at end of file
* PEP 692: Add newline at end of file
* PEP 633: Fix missing space before role
* Run sphinx-lint in pre-commit
* PEP 639: Remove rogue backticks
* PEP 372: Remove rogue backticks
* PEP 462: Add missing underscore after closing backtick in hyperlink
* PEP 481: Add missing underscore after closing backtick in hyperlinks
* PEP 507: Add missing underscore after closing backtick in hyperlinks
* PEP 453: Add missing underscore after closing backtick in hyperlinks, and convert to links
* PEP 534: Fix inline literal missing (escaped) space after literal
* PEP 372, 453, 462: Redirect BPO to GH
* Style: Further lighten table zebra stripes
* Style: Ensure consistent contrast for code blocks in zebra tables
* Style: Add padding around inline code literal BG to not be so tight
* Style: Add horizontal rules and header color to tables
* Style: Remove zebra striping from tables
* Style: Use more sensible color name for admonition + header color
As originally discussed in #2692 , this adds a three new custom directives intended to be used at the top of PEPs:
* `pep-banner`, a generic admonition banner that can be subclassed with an arbitrary message,
* `canonical-docs`, which renders a banner linking to a `Final` PEP's canonical documentation/specification.
* `canonical-pypa-spec`, a banner for packaging interoperability PEPs linking to the canonical PyPA specs.
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
* Fix canonical link tag to point to correct PEP URL
* Use shorter, standard HTML5 syntax for self-closing tags
* Avoid depr clip prop & use better supported transform prop in CSS
* Use strict mode in the color scheme JS
Since the basic admonition admonition styles are just applied to a couple individual admonitions, rather than admonitions in general, those other than "warning" and "note" won't display as admonitions at all. In addition to fixing that, this PR adds appropriate, standard colors for each of the additional admonition types in both light and dark mode.