Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[3.13] gh-127833: Docs: Add agrammar-snippet directive & replaceproductionlist (GH-127835)#129689

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
miss-islington wants to merge1 commit intopython:3.13
base:3.13
Choose a base branch
Loading
frommiss-islington:backport-58a4357-3.13

Conversation

miss-islington
Copy link
Contributor

@miss-islingtonmiss-islington commentedFeb 5, 2025
edited by github-actionsbot
Loading

As a first step toward aligning the grammar documentation with Python's actual
grammar, this overrides the ReSTproductionlist directive to:

  • use: instead of the::= symbol
  • add syntax highlighting for strings (using a Pygments highlighting class)

All links and link targets should be preserved. (Unfortunately, this reaches
into some Sphinx internals; I don't see a better way to do exactly what
Sphinx does.)

This also adds a new directive,grammar-snippet, which formats the snippet
almost exactly like what's in the source, modulo syntax highlighting and
keeping the backtick character to mark links to other rules.
This will allow formatting the snippets as in the grammar file
(file:///home/encukou/dev/cpython/Doc/build/html/reference/grammar.html).

The new directive is applied to two simple rules in toplevel_components.rst


(cherry picked from commit58a4357)

Co-authored-by: Petr Viktorinencukou@gmail.com
Co-authored-by: Blaise Pabonblaise@gmail.com
Co-authored-by: William Ferreirawqferr@gmail.com
Co-authored-by: bswckbartoszpiotrslawecki@gmail.com
Co-authored-by: Adam Turner9087854+aa-turner@users.noreply.github.com


📚 Documentation preview 📚:https://cpython-previews--129689.org.readthedocs.build/

…roductionlist` (pythonGH-127835)As a first step toward aligning the grammar documentation with Python's actualgrammar, this overrides the ReST `productionlist` directive to:- use `:` instead of the `::=` symbol- add syntax highlighting for strings (using a Pygments highlighting class)All links and link targets should be preserved. (Unfortunately, this reachesinto some Sphinx internals; I don't see a better way to do exactly whatSphinx does.)This also adds a new directive, `grammar-snippet`, which formats the snippetalmost exactly like what's in the source, modulo syntax highlighting andkeeping the backtick character to mark links to other rules.This will allow formatting the snippets as in the grammar file(file:///home/encukou/dev/cpython/Doc/build/html/reference/grammar.html).The new directive is applied to two simple rules in toplevel_components.rst---------(cherry picked from commit58a4357)Co-authored-by: Petr Viktorin <encukou@gmail.com>Co-authored-by: Blaise Pabon <blaise@gmail.com>Co-authored-by: William Ferreira <wqferr@gmail.com>Co-authored-by: bswck <bartoszpiotrslawecki@gmail.com>Co-authored-by: Adam Turner <9087854+aa-turner@users.noreply.github.com>
@encukou
Copy link
Member

Let's not merge the backport just yet. I'd like to see this change go through the release process first.

@encukouencukou marked this pull request as draftFebruary 5, 2025 15:27
@encukou
Copy link
Member

It should be merged together with a follow-up PR,#129692. If at all.

@AA-Turner
Copy link
Member

#130376 fixes thehelp() output. I think we should backport, especially as this PR is a pre-requisite for all of the work done on improving how we describe the grammar in the documentation. What do you think@encukou?

A

@encukou
Copy link
Member

I'm considering to backporting this for the syntax highlighting, but the upcoming grammar docs improvements are another matter. Those are tied to thecurrent grammar, verifying them is a fiddly manual process, and they're interlinked in complex ways -- a token in some grammar rule might need to move to another rule in another file, which Git won't catch as a conflict, and the nonexistent tests won't either (of course I'dlike to add tests, but that does require more automation, and in the current approach, rewriting the prose needs to come first.)

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@miss-islington@encukou@AA-Turner

[8]ページ先頭

©2009-2025 Movatter.jp